Relays in a multihop heterogeneous umts wireless communication system

ABSTRACT

Aspects relate to a Remote NodeB Relay that appears similar to a NodeB, a Radio Network Controller (RNC), and served mobile devices. Also provided is a Super-Light Router Relay that can provide better performance and QoS to served mobile devices while mitigating modifications to mobile devices, NodeBs, or interfaces between RNC and intermediary NodeBs. Aspects also relate to an Internet Protocol (IP) Relay that requires few, if any, modifications to mobile devices, NodeBs, or interfaces between RNC and intermediary NodeBs. Further, changes to an RNC and/or a core network can be mitigated though utilization of a strategic Relay Gateway.

CROSS-REFERENCE

The present application for patent is a Divisional and claims priorityto patent application Ser. No. 12/612,176, entitled “RELAYS IN AMULTIHOP HETEROGENEOUS UMTS WIRELESS COMMUNICATION SYSTEM” filed Nov. 4,2009, now allowed, which claims priority to U.S. Provisional ApplicationNo. 61/111,668 entitled “A METHOD FOR BASE STATION RELAYING IN AMULTIHOP HETEROGENEOUS UMTS WIRELESS COMMUNICATION SYSTEM” filed Nov. 5,2008, and U.S. Provisional Application No. 61/111,677 entitled “A METHODFOR SUPER-LIGHT ROUTER RELAYING IN A MULTIHOP HETEROGENEOUS UMTSWIRELESS COMMUNICATION SYSTEM” filed Nov. 5, 2008, which are assigned tothe assignee hereof and hereby expressly incorporated by referenceherein.

BACKGROUND

I. Field

The following description relates generally to wireless communicationsand more particularly to deployment of wireless relays in a wirelesscommunications network.

II. Background

Wireless communication systems are widely deployed to provide varioustypes of communication and to communicate information regardless ofwhere a user is located (e.g., inside or outside a structure) andwhether a user is stationary or moving (e.g., in a vehicle, walking).For example, voice, data, video, and so forth can be provided throughwireless communication systems. A typical wireless communication system,or network, can provide multiple users access to one or more sharedresources. A system can use a variety of multiple access techniques suchas Frequency Division Multiplexing (FDM), Time Division Multiplexing(TDM), Code Division Multiplexing (CDM), Orthogonal Frequency DivisionMultiplexing (OFDM), 3GPP Long Term Evolution (LTE), and others.

Wireless relays are deployed in wireless networks (such as UniversalMobile Telecommunications System (UMTS) High Speed Packet AccessEvolution (HSPA+), for example) to achieve coverage extension andcapacity increases at relatively low cost. However, the design of arelay (e.g., a multi-hop system) presents problems related to inclusionof relays in an air-interface system designed for single-hop. Further,there is motivation to mitigate changes that would require new ormodified user equipment (or mobile devices), network elements such asbase stations (NodeBs), and interfaces. Further, networking andprocessing should be harmonized for mobile devices on relays versusmobile devices not on relays.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

According to an aspect, a Remote NodeB Relay is described wherein thereare few, if any, modifications needed to mobile devices. Further, anymodifications needed to a Radio Network Controller (RNC) can be limitedsince the Remote NodeB Relay appears similar to a NodeB from theperspective of the RNC and the served mobile devices. Further, moreeffective performance and Quality of Service (QoS) can be provided tomobile devices served by the Remote NodeB Relay.

In accordance with another aspect, a Super-Light Router Relay isprovided wherein no (or very few) modifications are required to mobiledevices, NodeBs, or interfaces between RNC and intermediary NodeBs.Furthermore, better performance and QoS can be provided to mobiledevices served by the Super-Light Router Relay.

In yet another aspect, provided is an Internet Protocol (IP) Relay thatrequires few, if any, modifications to mobile devices, NodeBs, orinterfaces between RNC and intermediary NodeBs. Furthermore, in someaspects, changes to an RNC and/or a core network can be mitigated thoughutilization of a strategic Relay Gateway, even though the infrastructuremight not necessarily be all-IP (e.g., NodeBs and RNCs may not includecorresponding IP protocol layers).

An aspect relates to a method performed by a relay for routing data in amultihop communication network. Method includes employing a processorexecuting computer executable instructions stored on a computer readablestorage medium to implement the following acts. Method includescommunicating with a radio network controller though an intermediarybase station on behalf of a mobile device, wherein the communicating isa same signaling method as the signaling method used between radionetwork controller and intermediary base station. Further, methodincludes operating as at least one served mobile device, wherein theoperating comprises using a first set of lower layer air interfaceprotocol instances for a self-backhaul link between relay andintermediary base station and a second set of lower layer air interfaceprotocol instances for a wireless access link to the at least one servedmobile device.

Another aspect relates to a wireless communications apparatus thatincludes a memory and a processor. Memory retains instructions relatedto communicating on behalf of a mobile device with a radio networkcontroller through an intermediary base station and operating as atleast one served flow using a first set of lower layer air interfaceprotocol instances and a second set of lower layer air interfaceprotocol instances. Processor is coupled to memory and is configured toexecute instructions retained in memory.

Another aspect relates to a wireless communications apparatus thatincludes means for communicating with a radio network controller thoughan intermediary base station on behalf of a mobile device, wherein thecommunicating is a same signaling method as the signaling method usedbetween radio network controller and intermediary base station. Wirelesscommunications apparatus also includes means for operating as at leastone served mobile device. The operating comprises using a first set oflower layer air interface protocol instances for a self-backhaul linkbetween a relay and intermediary base station and a second set of lowerlayer air interface protocol instances for a wireless access link to theat least one served mobile device.

In accordance with some aspects, wireless communications apparatusincludes means for receiving, from intermediary base station, data forat least one served mobile device and at least a second served mobiledevice, wherein the data is received as a single flow. Also included canbe means for de-multiplexing the data received as the single flow andmeans for transmitting the data separately to the at least one servedmobile device and the at least the second served mobile device.According to some aspects, wireless communications apparatus includesmeans for receiving data from the at least one served mobile device andthe at least a second served mobile device. Also included can be meansfor multiplexing the data to create an aggregated data and means fortransmitting the aggregated data to intermediary base station.

Still another aspect relates to a computer program product comprising acomputer readable storage medium. Included in computer readable storagemedium is a first set of codes for causing a computer to communicate, onbehalf of a mobile device, with a radio network controller through anintermediary base station. Also included in computer readable storagemedium are a second set of codes for causing computer to operate as atleast one served flow using a first set of lower layer air interfaceprotocol instances and a second set of lower layer air interfaceprotocol instances.

Another aspect relates to at least one processor that includes a firstmodule that communicates on behalf of a mobile device and a secondmodule that operates as at least one served mobile device. At least oneprocessor also includes a third module that multiplexes anddemultiplexes received data to or from the at least one served mobiledevice.

Another related aspect is a method performed by a relay for conveyingdata in a wireless communications network. Method can include employinga processor executing computer executable instructions stored on acomputer readable storage medium to implement the following acts. Methodincludes serving at least one mobile device over a wireless access link,wherein the serving comprises using a first physical layer, data linklayer protocol stack and radio resource control server. Further, methodincludes connecting to a host radio network controller with a secondphysical layer, data link layer protocol stack and a radio resourcecontrol client, the connecting is over a wireless backhaul link to anintermediary base station. Additionally method includes communicatingwith host radio network controller with a remote radio network controlprotocol that is transparent to intermediary base station and mappingdata flows between wireless backhaul link and wireless access link withcoordination information communicated over remote radio network controlprotocol.

In a related aspect is a wireless communications apparatus that includesa memory and a processor. Memory retains instructions related to servingat least one mobile device over a wireless access link, connecting to ahost radio network controller and communicating with host radio networkcontroller with a remote radio network control protocol that istransparent to an intermediary base station. Memory retains furtherinstructions related to mapping data flows between a wireless backhaullink and wireless access link with coordination information communicatedover remote radio network control protocol. Processor is coupled tomemory and is configured to execute instructions retained in memory.

Another aspect relates to a wireless communications apparatus thatincludes means for serving at least one mobile device over a wirelessaccess link though use of a first physical layer, data link layerprotocol stack and radio resource control server. Also included inwireless communications apparatus is means for connecting to a hostradio network controller with a second physical layer, data link layerprotocol stack and a radio resource control client over a wirelessbackhaul link to an intermediary base station. Also included is meansfor communicating with host radio network controller with a remote radionetwork control protocol that is transparent to intermediary basestation. Further, wireless communications apparatus includes means formapping data flows between wireless backhaul link and wireless accesslink with coordination information communicated over remote radionetwork control protocol.

In accordance with some aspects, wireless communications apparatusincludes means for aggregating a connection to a served mobile devicewith another connection over a backhaul link and means for exchanginginformation with host radio network controller to map non-aggregatedaccess links for connections to an aggregated backhaul link. Accordingto some aspects, wireless communications apparatus includes means forrestricting at least one served mobile device from being in soft-handoffand a mobile device served by a base station from being in soft-handoffwith a relay.

Another aspect relates to a computer program product comprising acomputer readable storage medium. Included in computer readable storagemedium is a first set of codes for causing a computer to serve at leastone mobile device over a wireless access link, wherein the servingcomprises using a first physical layer, data link layer protocol stackand radio resource control server. Also included in computer readablestorage medium is a second set of codes for causing computer to connectto a host radio network controller with a second physical layer, datalink layer protocol stack and a radio resource control client, theconnecting is over a wireless backhaul link to an intermediary basestation. Also included is a third set of codes for causing computer tocommunicate with host radio network controller with a remote radionetwork control protocol that is transparent to intermediary basestation. Further, computer readable storage medium includes a fourth setof codes for causing computer to map data flows between wirelessbackhaul link and wireless access link with coordination informationcommunicated over remote radio network control protocol.

Yet another aspect relates to at least one processor that includes afirst module that serves at least one mobile device over a wirelessaccess link using a first physical layer, data link layer protocol stackand radio resource control server. Also included is a second module thatconnects to a host radio network controller with a second physicallayer, data link layer protocol stack and a radio resource controlclient over a wireless backhaul link to an intermediary base station.Further, the at least one processor includes a third module thatcommunicates with host radio network controller with a remote radionetwork control protocol that is transparent to intermediary basestation and a fourth module that maps data flows between wirelessbackhaul link and wireless access link with coordination informationcommunicated over remote radio network control protocol.

A further aspect relates to a method performed by a relay for conveyingrelayed data in a wireless communications network. Method includesemploying a processor executing computer executable instructions storedon a computer readable storage medium to implement the following acts.Method includes utilizing base station protocols to communicate as abase station to a served mobile device and mobile device protocols tocommunicate with an intermediary base station as a mobile device.Further, method includes carrying data transparently across at least oneintermediary network element, wherein relay has a relay self-backhaulinternet protocol to carry data to or from mobile device and to or froma relay gateway transparently across the at least one intermediarynetwork element.

Another aspect relates to a wireless communications apparatus thatincludes a memory and a processor. Memory retains instructions relatedto utilizing base station protocols to communicate as a base station toa served mobile device and mobile device protocols to communicate withan intermediary base station as a mobile device and carrying datatransparently across at least one intermediary network element.Processor is coupled to memory and is configured to execute instructionsretained in memory.

Still another aspect relates to a wireless communications apparatus thatsupports radio access technology interworking. Included in wirelesscommunications apparatus is means for communicating with base stationprotocols to communicate as a base station to a served mobile device andwith mobile device protocols to communicate with an intermediary basestation as a mobile device. Wireless communications apparatus alsoincludes means for carrying data transparently across at least oneintermediary network element.

Another aspect relates to a computer program product comprising acomputer readable storage medium. Included in computer readable storagemedium is a first set of codes for causing a computer to communicate, asa base station, with base station protocols and as a mobile device, withmobile device protocols. Also included in computer readable storagemedium is a second set of codes for causing computer to relay datatransparently across at least one intermediary network element.

A further aspect relates to at least one processor that includes a firstmodule that communicates with base station protocols to communicate as abase station to a served mobile device and with mobile device protocolsto communicate with an intermediary base station as a mobile device.Also included is a second module that carries data transparently acrossat least one intermediary network element.

Another aspect relates to a method performed by a base station forcommunicating in a multihop communication network. Method includesemploying a processor executing computer executable instructions storedon a computer readable storage medium to implement the following acts.Method includes communicating with a radio network controller with afirst backhaul communication protocol and with a relay with a secondbackhaul communication protocol, wherein first backhaul communicationprotocol includes data between relay and radio network controller.Further, method includes forwarding data for relay on second backhaulcommunication protocol based on information included in first backhaulcommunication protocol.

To the accomplishment of the foregoing and related ends, one or moreaspects comprise features hereinafter fully described and particularlypointed out in the claims. The following description and annexeddrawings set forth in detail certain illustrative features of one ormore aspects. These features are indicative, however, of but a few ofvarious ways in which principles of various aspects may be employed.Other advantages and novel features will become apparent from thefollowing detailed description when considered in conjunction with thedrawings and the disclosed aspects are intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a schematic representation of a comparison between asingle hop network and a multi-hop network.

FIG. 2 illustrates a schematic representation of protocol end-points forRNC pseudo-transparent aspects disclosed herein.

FIG. 3 illustrates a protocol architecture for an RNC pseudo-transparentaspect, as discussed herein.

FIG. 4 illustrates an abstraction (logical) view of RNC Iub Interfaces,according to an aspect.

FIG. 5 illustrates a schematic representation of air-interface protocolend-points for an RNC Agent, according to an aspect.

FIG. 6 illustrates a protocol architecture for an RNC Agent, accordingto an aspect.

FIG. 7 illustrates a schematic representation of protocol end-points forRNC remote signaling, according to an aspect.

FIG. 8 illustrates a protocol architecture for RNC Remote Signaling,according to an aspect.

FIG. 9 illustrates self-backhaul aggregation, according to an aspect.

FIG. 10 illustrates a self-backhaul aggregation per priority flow,according to an aspect.

FIG. 11 illustrates a schematic representation of air-interfaceprotocols and their end-points along a path from mobile device to corenetwork for a Super-Light Router Relay, according to an aspect.

FIG. 12 illustrates a protocol architecture of a Super-Light RouterRelay and related network elements, according to an aspect.

FIG. 13 illustrates a schematic representation of self-backhaulaggregation, according to an aspect.

FIG. 14 illustrates a schematic representation of self-backhaulaggregation per priority flow, according to an aspect.

FIG. 15 illustrates a schematic representation with an IP Relay,according to an aspect.

FIG. 16 illustrates a schematic representation of an architecturewithout a relay, according to an aspect.

FIG. 17 illustrates a schematic representation of a baselinearchitecture with no relays, according to an aspect.

FIG. 18 illustrates an architecture with all mobile devices on IPRelays, according to an aspect.

FIG. 19 illustrates a schematic representation of protocol end-pointswith all mobile devices on relays, according to an aspect.

FIG. 20 illustrates a schematic representation of a Relay Non-RelayGateway, according to an aspect.

FIG. 21 illustrates protocols for a Relay Non-Relay Gatewayarchitecture, according to an aspect.

FIG. 22 illustrates a Relay Non-Relay Gateway Break-Out, according to anaspect.

FIG. 23 illustrates a Relay Access Gateway schematic representation,according to an aspect.

FIG. 24 illustrates a Relay Access Gateway protocol architecture,according to an aspect.

FIG. 25 illustrates a Relay Access Gateway Break-Out, according to anaspect.

FIG. 26 illustrates a network design for a Relay Core Gateway for aRelay Gateway, according to an aspect.

FIG. 27 illustrates Relay Core Gateway Protocols from a protocolviewpoint, according to an aspect.

FIG. 28 illustrates a Relay Core Gateway Break-Out, according to anaspect.

FIG. 29 illustrates a method for routing data in a multihopcommunication network.

FIG. 30 illustrates a method for communicating in a multihopcommunication network.

FIG. 31 illustrates a method for conveying data in a wirelesscommunications network.

FIG. 32 illustrates a method for conveying relayed data in a wirelesscommunications network.

FIG. 33 illustrates an example system that facilitates routing data in amultihop communication network, according to an aspect.

FIG. 34 illustrates an example system that facilitates conveying data ina wireless communications network, according to an aspect.

FIG. 35 illustrates an example system that facilitates conveying relayeddata in a wireless communications network, according to an aspect.

FIG. 36 illustrates an example system that facilitates conveying relayeddata in a wireless communications network, according to an aspect.

FIG. 37 illustrates a system that facilitates relaying in a multi-hopcellular communications system, in accordance with one or more of thedisclosed aspects.

FIG. 38 illustrates an exemplary wireless communication system,according to various aspects.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that such aspect(s) maybe practiced without these specific details. In other instances,well-known structures and devices are shown in block diagram form inorder to facilitate describing these aspects.

As used in this application, the terms “component”, “module”, “system”,and the like are intended to refer to a computer-related entity, eitherhardware, firmware, a combination of hardware and software, software, orsoftware in execution. For example, a component may be, but is notlimited to being, a process running on a processor, a processor, anobject, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on acomputing device and the computing device can be a component. One ormore components can reside within a process and/or thread of executionand a component may be localized on one computer and/or distributedbetween two or more computers. In addition, these components can executefrom various computer readable media having various data structuresstored thereon. Components may communicate by way of local and/or remoteprocesses such as in accordance with a signal having one or more datapackets (e.g., data from one component interacting with anothercomponent in a local system, distributed system, and/or across a networksuch as the Internet with other systems by way of the signal).

Furthermore, various aspects are described herein in connection with amobile device. A mobile device can also be called, and may contain someor all of the functionality of a system, subscriber unit, subscriberstation, mobile station, mobile, wireless terminal, node, device, remotestation, remote terminal, access terminal, user terminal, terminal,wireless communication device, wireless communication apparatus, useragent, user device, or user equipment (UE), and the like. A mobiledevice can be a cellular telephone, a cordless telephone, a SessionInitiation Protocol (SIP) phone, a smart phone, a wireless local loop(WLL) station, a personal digital assistant (PDA), a laptop, a handheldcommunication device, a handheld computing device, a satellite radio, awireless modem card, and/or another processing device for communicatingover a wireless system. Moreover, various aspects are described hereinin connection with a base station. A base station may be utilized forcommunicating with wireless terminal(s) and can also be called, and maycontain some or all of the functionality of, an access point, node, NodeB, e-NodeB, e-NB, or some other network entity.

Various aspects or features will be presented in terms of systems thatmay include a number of devices, components, modules, and the like. Itis to be understood and appreciated that various systems may includeadditional devices, components, modules, and so forth, and/or may notinclude all devices, components, modules, and so on, discussed inconnection with the figures. A combination of these approaches may alsobe used.

Additionally, in the subject description, the word “exemplary” (andvariants thereof) is used to mean serving as an example, instance, orillustration. Any aspect or design described herein as “exemplary” isnot necessarily to be construed as preferred or advantageous over otheraspects or designs. Rather, use of the word “exemplary” is intended topresent concepts in a concrete manner.

FIG. 1 illustrates a schematic representation 100 of a comparisonbetween a single hop network 102 and a multi-hop network 104. Single-hopnetwork 102 (or single-hop access) includes a mobile device 106 thatcommunicates with a NodeB 108 over a wireless access link 110. Further,NodeB 108 communicates with an RNC 112 over a wired backhaul link 114.

Multi-hop network 104, is similar to single-hop network 102; however, arelay 116 is inserted between mobile device 106 and NodeB 108. Mobiledevice 106 communicates over wireless access link 110 to relay 116 andrelay 116 communicates with NodeB 108 over a wireless backhaul link 118.Further, NodeB 108 communicates with RNC 112 over wireless backhaul link114. Backhaul link and access link are different links over differentmediums (e.g., different carrier, time (e.g., retransmission slots),spatial dimension, and so on).

The deployment of relays (which can be inexpensive) in wireless networksto achieve wireless multi-hoping within the domain of the air-interfacehas the potential to: (1) extend coverage to holes or poor coverageareas (e.g., pockets of a geographic area that are without coverage),(2) increase capacity, by cell splitting gain, and (3) offload resourcerequirements from base stations. While pico cells or femto cells (e.g.,home NodeBs) may be motivated by similar goals, such cells generallyrequire either wired backhaul (such as fiber, cable, or digitalsubscriber line (DSL)) or wireless backhaul over a different wirelesstechnology (e.g., microwave). Femto cells may also have restrictions onwhich mobile devices can associate with the femto cells and thus haveadditional interference issues.

Repeaters are sometimes considered a sub-class of relays. However,repeaters generally amplify and forward an “unclean” copy of signals.Therefore, relays can amplify interference and noise as well as theuseful signal. Further, relays may be unnecessarily redundant. This lowprotocol layer level of repeaters also means the repeaters generally donot take advantage of different medium and link conditions (channelquality) on different hops. Furthermore, emergency or (E-911)capabilities are important and repeaters or low-layer-only devices maypresent a challenge for identifying user location based on serving nodelocation.

Relays may act similar to base stations (NodeBs), from the point of viewof mobile devices, although typically with smaller coverage areas thanmicro cells or macro cells (e.g., similar to pico cells or femto cells).In fact, it can be beneficial if mobiles devices do not have toknowingly distinguish between a relay and a NodeB at all, in order tosupport legacy mobile devices (e.g., no changes needed to existingmobile devices). However, while relays are similar to NodeBs, the relayscan “self-backhaul”. “Self-backhaul” refers to relay 116 connectingthrough wireless backhaul link 118 to (regular) NodeB 108 and NodeB 108connecting to RNC 112, as illustrated in FIG. 1. Relays thus canmitigate issues associated with wiring backhaul to the relay site.

However, these characteristics of relays result in at least two issues.First, the backhaul payload is carried part-way over a wireless link(with wireless characteristics) instead of only a wired link. Second,relays, which act as NodeBs for mobile devices and as mobile devices fortheir self-backhaul, are inserted (merged) into a single-hop accessnetwork architecture.

These two issues each present a number of complex and inter-relatedchallenges. For example, wired backhauls for UMTS can be carried over anIub interface between RNC 112 and NodeB 108. An Iub link can carry suchinformation and signaling as: operation and maintenance (O&M), handover,resource allocation, transport traffic management, timing andsynchronization, NodeB power control, admission control, measurement andreporting, and other information.

The Iub interface can be carried by Asynchronous Transfer Mode (ATM)adaptation protocols and ATM MAC (Medium Access Control) layers or UserDatagram Protocol/Internet Protocol (UDP/IP) protocols. However, whilethere may be standards for the backhaul, these standards may not bestrictly adhered to (in contrast to protocols between other networkelements). Additionally, signaling from network control points, such asRNC to the relay (not to mobile devices served by relay), may addadditional overhead for the backhaul to carry (e.g., in addition to userdata and user control signaling). For example, Iub overhead from RNC 112to NodeB 108 may be as much as around 10% for NodeB control and anadditional 10% (more or less) for mobile devices. In addition, RNC 112may interface with many NodeBs (although only one is illustrated forpurposes of simplicity). Finally, when relay 116 uses the sametechnology and same signaling space as mobile devices, relay 116 is ineffect sharing the backhaul with other mobile devices (typically thosenot served by relay 116 but by neighboring NodeB (not shown) orhost-NodeB 108), but potentially increasing latency for those mobiledevices served by relay 116 due to additional hop(s). In addition,prioritization and Quality of Service (QoS) should be maintained notonly for relay versus actual mobile devices served by intermediary NodeBbut also between mobile devices served by relay.

The design of an IP Relay is even further complicated for UMTS HSPA+because user IP protocols are above the NodeB 108, RNC 112 (accessstratum), and even above the Serving GPRS (General Packet Radio Service)Support Node (SGSN). In UMTS HSPA+, the GPRS Gateway Support Node (GGSN)(core network) is the IP protocol end-point. Inserting a relay withupper layers up to IP or higher into the chain of connections betweenNodeB 108 and mobile device 106 changes the protocol scenario. This isbecause other intermediary nodes in the UTRAN (Universal TerrestrialRadio Access Network) do not have the corresponding IP layers and mobiledevices on relays may have to pass through an additional Relay Gatewayinserted elsewhere in the chain of connections (e.g. in the corenetwork). However, both protocol configurations should be supported inorder for the system to support mobile devices on relays and mobiledevices not on relays.

In accordance with some aspects, relay 116 can be configured to appearas a NodeB to RNC 112 and to mobile devices 106 and to appear as amobile device to an intermediary NodeB 108. In accordance with theseaspects, relay 116 will be referred to herein as Remote NodeB Relay. Inaccordance with these aspects, RNC 112 delivers user data and signalingas well as signaling for Remote NodeB Relay through intermediary NodeB.Remote NodeB Relay has NodeB functionality layers, however, there isadditional protocol to carry the backhaul over/past the hosting NodeBand to (modified) RNC. There are three main aspects disclosed hereinrelated to a Remote NodeB Relay that provides the functionality of aNodeB from the access link perspective. These three aspects of a RemoteNodeB Relay relate to different aspects utilized to interface relay withRNC and/or NodeB. These three aspects are referred to as “RNCPseudo-Transparent”, “RNC Agent”, and “RNC Remote Signaling”, which willnow be described in further detail.

A first aspect of Remote NodeB Relay is referred to as “RNCPseudo-Transparent”. In the RNC Pseudo-Transparent aspect, a Relay toRNC interface may be the same as a NodeB to RNC interface but tunneledover the intermediary NodeB to RNC interface (e.g. Iub tunneled overIub). This aspect will be described in further detail with reference toFIG. 2, FIG. 3, and FIG. 4 below.

FIG. 2 illustrates a schematic representation 200 of protocol end-pointsfor RNC pseudo-transparent aspects disclosed herein. FIG. 3 illustratesa protocol architecture 300 for RNC pseudo-transparent aspects, asdiscussed herein. Illustrated are blocks that represent a core network(CN 202), an RNC 204, a NodeB 206, a Remote NodeB Relay 208, and amobile device 210. Mobile device 210 communicates with Remote NodeBRelay 208 over an Access Link 212, which can be a wireless access link.Remote NodeB Relay 208 communicates with NodeB 206 over a Self-BackhaulLink 214, which can be wireless. NodeB 206 communicates with RNC 204over an Iub Interface 216, which can be wired or wireless. RNC 204communicates with CN 202 over an Iu interface 218. RNC 204 treats aninterface 302 to Remote NodeB Relay 208 similar to interface (TubInterface 216) to NodeB 206. Thus, RNC 204 treats interface 302 as anembedded Iub interface with a full Iub stack protocol 304 (such asasynchronous transfer mode (ATM) or user datagram protocol/Internetprotocol (UDP/IP)).

Interface 306 between Remote NodeB Relay 208 and RNC 204 may be the sameas a NodeB 206 to RNC 204 interface (e.g., Iub interface 216). However,interface 306 is tunneled over intermediary NodeB 206 to RNC 204interface (e.g. Iub tunneled over Iub). The term “tunneling” means afirst protocol (e.g. Iub) is treated as data as far as a second protocol(e.g. Iub) is concerned. Thus, as illustrated, the second protocoldistinguishes only control information for NodeB 206 to RNC 204interface (e.g., Iub interface 216) and what it views only as data(which is actually embedded control and data for Remote NodeB Relay 208to RNC 204 interface). Since the first protocol may distinguish controland actual data information, the end-point (Remote NodeB Relay 208) isable to separate control and actual data once this embedded portion isextracted by the second protocol.

However, since this interface must be communicated over the first hop tothe intermediary NodeB 206, the protocols may be passed through the Iubstack for that link. This results in overhead. Nevertheless, only oneset of Iub stack protocols are passed over the self-backhaul link 214since NodeB 206 is the end-point for the underlying Iub backhaul stack.

An advantage of the disclosed architecture is that Remote NodeB Relay208 appears the same as NodeB 206 from the interface perspective.Another advantage is that Remote NodeB Relay 208 has a distinct NodeBidentity and thus can accommodate E-911 emergency services. Depending onwhether aggregation (whether relay acts as one mobile device or multiplemobile devices (per mobile device served by relay) is used or is notused (which will be discussed in further detail below), the architecturemay also be completely transparent to NodeBs (requiring no NodeBmodifications). Furthermore, RNC 204 modifications can be encapsulatedinto an additional instance(s) of already supported common protocolstacks.

From a conceptual view, the connection appears as in FIG. 4, whichillustrates an abstraction (logical) view of RNC Iub Interfaces 400,according to an aspect. Illustrated are an RNC 402 with Iub Interfaces404 to multiple NodeBs 406 and multiple Remote Relay NodeBs 408. Itshould be noted that the number of NodeBs 406 and Remote Relay NodeBs408 can be fewer or more than those shown, as this figure is for examplepurposes only.

A second aspect of Remote NodeB Relay, referred to as “RNC Agent”,includes a relay to RNC interface that can be controlled through aninterface between intermediary NodeB and RNC where NodeB, in turn,controls relay. This is similar to the RNC controlling a NodeB (e.g., asan agent of the RNC). In the RNC Agent aspect, hosting NodeB controlsRemote NodeB Relay as if Remote NodeB Relay is part of hosting NodeB.FIG. 5 illustrates a schematic representation 500 of air-interfaceprotocol end-points for RNC Agent, according to an aspect. FIG. 6illustrates a protocol architecture 600 for RNC Agent, according to anaspect.

Illustrated are representations of CN 502, RNC 504, NodeB 506, RemoteNodeB Relay 508, and mobile device 510. In this aspect, Remote NodeBRelay 508 is controlled with signaling from NodeB 506, which is in turncontrolled by RNC 504. NodeB 506 is an agent for RNC 504, acting onbehalf of RNC 504, to instruct Remote NodeB Relay 508 and to deliveruser data and signaling to Remote NodeB Relay 508. In this aspect,signaling to NodeB 506 is extended. This Extended Signaling (ES) service(Extended Iub Sig 512 (FIG. 5) and ES 602, 604 (FIG. 6)) at RNC 504allows Remote NodeB Signaling (RNS) function at RNC 504 to instructNodeB 506 on how to control Remote NodeB Relay 508. NodeB ExtendedSignaling (ES) client receives the instructions or notifications and mayrespond with reports or indications. NodeB 506 uses the receivedinformation to control Remote NodeB Relay 508 using a Relay Signaling(RS) service (Remote Iub Sig 514 (FIG. 5) and RS 606, 608 (FIG. 6)). TheRS 606, 608 can also be used for various functions such as measurementand reporting by Remote NodeB Relay 508. Remote NodeB Relay 508 has aRelay Signaling client (RS 608) which communicates with RS service (RS606) at NodeB 506 and performs the functions typical for a NodeB.

As illustrated in FIG. 6 the RNC Agent aspect can include modificationsand/or extensions to the Iub signaling to accommodate control of RemoteNodeB Relay 508 by the intermediary NodeB on behalf of RNC 504 andreporting from Remote NodeB Relay 508. NodeB 506 (and thus ExtendedSignaling (ES)) should be able to distinguish data for mobile devices(e.g., mobile device 510) versus signaling for Remote NodeB Relay 508 sothat NodeB 506 can use the Remote Signaling (RS) for signaling RemoteNodeB Relay 508 and bypass this for user data and user signaling (e.g.,for mobile device 510).

For example, not only would NodeB 506 need to know about mobile devicesbeing served by Remote NodeB Relay 508, so that user data and control(e.g., Radio Resource Control (RRC) signaling, System Information Blocks(SIBs), and so forth) can be forwarded, but also about the configurationof relay as a remote NodeB (see above list of features for which asubset may be required between NodeB 506 and Remote NodeB Relay 508). Inaccordance with some aspects, some features may not be supported atRemote NodeB Relay 508, such as random access or call setup. In thiscase, mobile devices may be restricted from using these features onRemote NodeB Relay 508 or the communications may be forwarded to NodeB506 or RNC 504 to handle.

It should be noted that in accordance with the RNC Agent aspect theremight need to be modifications on NodeB 506 to add the new ExtendedSignaling (ES 604) client and to add the Relay Signaling (RS 606)service. In accordance with some aspects, ES 604 and RS 606 are combinedinto one function. Thus, Remote NodeB Relay 508 is not transparent toNodeB 506 for the RNC Agent aspect. However, Remote NodeB Relay 508 canbe transparent from the perspective of mobile device(s) 510.

A third aspect of the Remote NodeB Relay is referred to as “RNC RemoteSignaling”. In this aspect, Relay to RNC interface may be the same asthe interface (Tub) protocol level as NodeB to RNC interface but notduplicative of the underlying backhaul protocols (Iub thin signalingover Iub).

FIG. 7 illustrates a schematic representation 700 of protocol end-pointsfor RNC remote signaling, according to an aspect and FIG. 8 illustratesa protocol architecture 800 for RNC Remote Signaling, according to anaspect. Illustrated by blocks are CN 702, RNC 704, NodeB 706, RemoteNodeB Relay 708, and mobile device 710. For the RNC Remote Signalingaspect, RNC 704 additions include only a signaling and control layercalled the Remote NodeB Signaling (RNS 712 (FIG. 7) and RNS 802 (FIG.8)) service (not an entire embedded Iub stack). This service (e.g., RNS802) interfaces with a counterpart RNS client 804 at Remote NodeB Relay708. RNS 712, 802, 804 may use the same messaging as Iub but does notrequire the underlying link, medium access, or physical layer protocolsbecause RNS 712, 802, 804 is carried over the Iub stack for the firsthop and the air-interface stack for the second hop. Thus, the RNC RemoteSignaling aspect has less overhead than the RNC Pseudo-Transparentaspect (discussed above) and may be less complex than the RNC Agentaspect (discussed above). However, the RNC Remote Signaling aspect mayrequire modification to be flexible and efficiently carried over withthe lower-layer air-interface stack as well the Iub stack.

Further, depending on whether aggregation is used or is not used (aswill be discussed below), the architecture 800 (e.g., RNS 712, 802, 804)may also be transparent to NodeBs (requiring no NodeB modifications),which is an advantage relative to the RNC Agent aspect. Transparency toNodeB 706, is an advantage. For example, there can be one RNC 704 andhundreds of NodeBs (only one of which is shown). Therefore, if RNS 712,802, 804 is transparent to the hundreds of NodeBs, it means that thereare no changes needed to the hundreds of NodeBs. Furthermore, RNCmodifications are encapsulated into an additional inserted layer (RNS712 shown in FIG. 7).

RNS 712 distinguishes user data and signaling (from RNC 704 destined tothe user (or mobile device 710)) from relay signaling (from RNC 704destined to Remote NodeB Relay 708). RNS does not necessarily have toimplement all signaling supported by a typical NodeB since Remote NodeBRelay 708 may have limited functionality compared to a NodeB. Forexample, Remote NodeB Relay 708 may not transmit all overhead channels.However, the RNS may support additional features unavailable in a NodeB,such as multiplexing and de-multiplexing functions to aggregate usersover the self-backhaul and Iub Backhaul. In other words, RNC 704 andRemote NodeB Relay 708 coordinate to achieve aggregation transparently(or unbeknownst) to NodeB 706.

Modifications to NodeB 706 may be limited (or there may be nomodifications needed) for RNC Remote Signaling. Further, the overhead islimited or minimal, and Remote NodeB Relay 708 can be efficiently andeffectively controlled by RNC 704.

Alternatively, there are variations between the RNC Pseudo-Transparentaspect and the RNC Remote Signaling aspect with a subset of the stackcomponents. Additional protocols add overhead, but can benefit RNC toRelay connection since it is carried over a wireless link instead of awired link. For example, a wireless link layer retransmission capabilitycan be beneficial to recover from lost signaling intended for relay 708itself.

In the three aspects described above (RNC Pseudo-Transparent, RNC Agent,and RNC Remote Signaling), relay 208, 508, 708 has at least one MAC(MAC-hs/e 308, 610, 806) instance for the backhaul and one instance(MAC-hs/e 310, 612, 808) for the access link per mobile device (only oneof which is shown). This allows the relay 208, 508, 708 to takeadvantage of potentially different conditions on the backhaul link'swireless medium and the access link's wireless medium. Furthermore, itallows relay 208, 508, 708 to do more than mere repeating of MAC frames(although this can be done). In other words, relay 208, 508, 708 canselect a MAC frame format for access link (or backhaul link) suitablefor that link, according to a channel quality indication (or the like)for that link. Furthermore, this separation of links at the lower-MAClevel presents the possibility for aggregating mobile device trafficover the backhaul. Thus a single MAC frame on the backhaul may hold datafor multiple mobile devices. relay 208, 508, 708 de-multiplexes the dataand creates separate MAC frames for mobile devices on the access link.In reverse, relay 208, 508, 708 multiplexes data from frames receivedfrom mobile devices into one frame for the backhaul.

FIG. 9 illustrates self-backhaul aggregation 900, according to anaspect. Aggregation relates to the situation where there are multiplemobile devices (e.g., n mobile devices) being served by Remote NodeBRelay. On an uplink (e.g., communication from mobile device), eachmobile device can be transmitting a pilot. For aggregation, Remote NodeBRelay does not operate as n mobile device instead, Remote NodeB Relayoperates as a single mobile device and transmits a single pilot.Aggregation can be at an IP level, wherein an IP packet can contain IPpackets from multiple mobile devices and the IP packet is de-aggregatedlater (e.g., at a gateway or RNC).

Illustrated are representations of a NodeB 902 and a first set of mobiledevices 904 served directly by NodeB 902 over NodeB Access Links 906,which can be wireless. Also illustrated is a Remote NodeB Relay 908 thatcommunicates with NodeB 902 over a Self-Backhaul Link 910, which can bewireless. In this figure, Remote NodeB Relay 908 is communicating with asecond set of mobile devices 912 over Relay Access Links 914, which maybe wireless.

In accordance with the illustrated aspect, mobile device traffic can beaggregated on the backhaul link(s). In other words, instead of relay 908acting as one mobile device per mobile device it serves (or one backhaulflow per mobile device access link flow), the Relay to NodeB or Relay toRNC links can be combined into one connection or flow. NodeB 902 canreceive un-aggregated traffic from the RNC (not shown), buffer theindividual traffic flows in NodeB 902, and then aggregate onself-backhaul link 910.

However, NodeB 902 may then require knowledge of the content of theaggregated frames in order to properly prioritize the aggregatedself-backhaul link 910 relative to mobile devices 904 served directly byNodeB 902. This problem can be partially addressed by only aggregatingtraffic of like priority. FIG. 10 illustrates a self-backhaulaggregation per priority flow 1000, according to an aspect. Having anaggregated flow per priority in the union or priority levels of relayserved mobile device 912 flows. Relay 908 can use signaling from thenetwork to know how to multiplex or de-multiplex each flow from NodeB902. This signaling can be embedded in the frames within the flow (e.g.,addressing the mobile device (flow)).

However, if NodeB 902 uses a scheduling algorithm proportionally fairfor users (flows), then a scheduler 916 might not take into account thefact that the aggregated flows represent multiple users or the ratio ofusers on relay 908 to those on the direct NodeB Access Link 906. Thus,NodeB 902 may be modified to receive control information from relay 908(or from RNC) indicating the prioritization and scheduling preference togive to the relay self-backhaul link 910 (and properly account forbilling of users). This may be accomplished by modifying the NodeBscheduler algorithm to bias relay 908 according to the number orpriority of mobile devices (flows) on relay 908 whose self-backhaul isthrough that intermediate NodeB 902. Thus, Remote NodeB Relay 908architecture may have NodeB modifications for efficient, highperformance operation but may be deployed without aggregation or withoutNodeB changes at the tradeoff of performance, functionality, orefficiency. In the case without aggregation, the flow for each user(e.g., mobile device) can be mapped to a separate MAC-d flow on thebackhaul so that the NodeB scheduler 916 does not need to know whichuser (e.g., mobile device) the flow is destined for in order to schedulethe transmission to relay 908.

With a Remote NodeB Relay 908, there are at least two possibleapproaches for aggregation: (1) no changes to Node B or (2) changes toNode B. Without making changes to NodeB, aggregation may be achieved inthis architecture by mapping each flow of each user to a separate MAC-dflow. The Remote NodeB Signaling (RNS) service can be used to set upcontrol information at the Remote NodeB Relay, mapping a MAC-d flow to auser's flow. However, since the number of MAC-d flows per mobile devicemay be limited (e.g., to around eight), this can allow only a limitedamount of aggregation (e.g., sets of two, three, or more, aggregatedmobile devices since mobile devices may have multiple flows).

By making changes to Node B, more flexible aggregation compared to thecase of no changes to NodeB can be achieved. An alternative is for NodeBto aggregate data from flows of multiple mobile devices in the same MACpacket, and add mobile device identifiers (e.g., High Speed-DownlinkShared Channel (HS-DSCH) Radio Network Temporary Identifiers (H-RNTIs))to allow Remote NodeB Relay to demultiplex flows. In another aspect,this involves changing the MAC-hs header and changes to the NodeB.

Further, in at least the aspects related to a Remote NodeB Relay, thereare few (if any) modifications needed to mobile devices and modificationto RNC are limited since Remote NodeB Relay appears as a NodeB to theRNC as well as the served mobile devices. Additionally, effectiveperformance and QoS can be provided to mobile devices served by RemoteNodeB Relay. Another advantage is that Remote NodeB Relay appearssimilar to a NodeB from the interface perspective. A related advantageis that the Remote NodeB Relay has a distinct NodeB identity and, thus,can accommodate E-911 emergency services. Depending on whetheraggregation is used (or not used), the architecture may also betransparent to nodeBs (necessitating no NodeB modifications. Further,RNC modifications can be encapsulated into an additional instance(s) ofalready supported common protocol stacks. Modifications to NodeB can belimited or none at all, the overhead is limited or minimal, and theRemote NodeB Relay can be efficiently and effectively controlled by theRNC.

In accordance with some aspects, Remote NodeB Relay can include memoryoperatively coupled (internally or externally) to Remote NodeB Relay. Aprocessor can be coupled to memory and can be configured to executeinstructions retained in memory. Memory can retain instructions relatedto communicating on behalf of a mobile device with a radio networkcontroller through an intermediary base station and operating as atleast one served flow using a first set of lower layer air interfaceprotocol instances and a second set of lower layer air interfaceprotocol instances. The instructions related to communicating use a samesignaling method as the signaling method used between the radio networkcontroller and the intermediary base station.

According to some aspects, memory retains further instructions relatedto receiving data as a single flow for the at least one served flow andat least a second served flow, de-multiplexing the data received as thesingle flow, and transmitting the data separately to the at least oneserved flow and the at least a second served flow. Additionally oralternatively, memory retains further instructions related to receivingdata from at least two user flows, multiplexing the data to create anaggregated data, and transmitting the aggregated data to theintermediary base station.

In accordance with some aspects, Remote NodeB Relay includes at leastone processor (which can be operatively connected to memory). Processorincludes a first module that communicates on behalf of a mobile deviceand a second module that operates as at least one served mobile device.Processor also includes a third module that multiplexes anddemultiplexes received data to or from the at least one served mobiledevice.

FIG. 11 illustrates a schematic representation 1100 of air-interfaceprotocols and their end-points along the path from mobile device to corenetwork for a Super Light Router Relay, according to an aspect.According to some aspects, relay is a referred to as a Super-LightRouter Relay. In this aspect, a Remote RNC Protocol (RRP) is utilizedbetween RNC and relay, which is transparent to intermediate base station(or NobeB). In this aspect, relay utilizes a first physical layer, datalink layer protocol stack and radio resource control server to serve amobile device over a wireless access link. Further, relay utilizes asecond physical layer, data link layer protocol stack and radio resourcecontrol client to connect to an RNC through a wireless backhaul link toNobeB. Relay communications with RNC using a remote radio networkcontrol protocol that is transparent to NobeB. Further, relay maps dataflows between wireless backhaul link and wireless access link utilizingcoordination information communicated over the remote radio networkcontrol protocol.

Illustrated are a core network (CN 1102), an RNC 1104, a NodeB 1106, aRelay (Super-light RNC Relay 1108) and a mobile device 1110 (or UserEquipment (UE)). Mobile device 1110 communicates with Relay 1108 overAccess Link 1112, which can be a wireless link. Relay 1108 communicateswith NodeB 1106 over a Self-Backhaul Link 1114, which can be a wirelesslink. NodeB 1106 communicates with RNC 1104 over Iub 1116, which can bewireless or wired. RNC 1104 communicates with CN over an Iu 1118. FIG.12 illustrates a protocol architecture 1200 of the Super-light RouterRelay and related network elements, according to an aspect, and will bediscussed in combination with FIG. 11.

In accordance with this aspect, there is a Super-Light Router Relay 1108(or Super-Light RNC Relay) and a Remote RNC Protocol (RRP 1120) betweenhost RNC 1104 and Relay 1108, which are transparent to the intermediateNodeB(s) 1106.

Super-Light Router Relay 1108 has air-interface protocols up to at leastlayer 2 (generally MAC 1122 and RLC 1124), for both backhaul and accesslinks domains, and thus can take advantage of the different medium andlink conditions. RRP 1120 provides an efficient means to transporthigher layer user data, control signaling and conduct coordination withhost RNC 1104 transparent to intermediate NodeB(s) 1106.

Super-Light Router Relay 1108 can help overcome obstacles (describedabove) by terminating air-interface protocols at strategic points in thenetwork, making some upper layer protocol changes invisible ortransparent to intermediate nodes (e.g. intermediary NodeB 1106), andmanaging a separate air-interface stack for mobile devices 1110 thatRelay 1108 serves. The latter also has performance advantages because,for example, having RLC per link allows for fast per-link failurerecovery. Increased route-trip time due to multi-hop and in combinationwith high data rates may cause significant link failure recovery delayin an end-to-end RLC situation. With two RLCs in a two-hop system, theindividual RLCs can advance re-transmission windows and re-sequenceframes independently. Furthermore, having these layer 2 protocols (MAC1122 and RLC 1124) allows for segmentation, concatenation,retransmission, in-sequence or out-of-sequence delivery, flow controland possibly ciphering per user (e.g., mobile device 1110) per link perflow. This allows for the option of aggregating mobile device flows onthe backhaul above the MAC frame level. Also, with flow control perlink, there may be more flexibility in a Relay's implementation (forexample, less memory may be needed because it can be managed preciselyper flow and overall).

Further, by terminating these lower layer protocols at Super-LightRouter Relay 1108, only higher layer signaling (generally less timesensitive and less overhead) needs to be communicated. RRP 1120 canaccomplish this function, as well as other functions.

For the following discussion, the Relay's stack(s) for the “Relay actingas mobile device(s)” (e.g., on the Self-Backhaul Link 1114) will bereferred to as the Relay's Backhaul Stack or “Backhaul face”. TheRelay's stack(s) for the “Relay acting as serving cell” will be referredto as the Relay's Access Stack or “Access face”.

In the Access face, Super-Light Relay 1108 has one or more UMTS stacksfor operating over the backhaul link, in which it appears as a mobiledevice (or mobile devices) to regular NodeB(s) 1106. In accordance withan aspect, those stacks each include Physical Layer 1202, MAC 1204, andRLC 1206 layers. On top of that, it has the Remote RNC Protocol (RRP1208) for coordination with hosting RNC 1104. The Super-Light Relay'sAccess Stack comprises the functions of (1) Relay NodeB (PHY andMAC-hs/e), (2) Relay Radio Resource Control (RRC server), (3) RelayAccess Link MAC and RLC, and (4) Relay Host-RNC Coordination Function(HCF).

On the Backhaul face, the Super-Light Relay has a UMTS stack per mobiledevice it serves through the Relay Access Link. The Super-Light Relay'sBackhaul Stack includes the functions of (1) Relay mobile device(s)(PHY, MAC-hs/e, MAC, and RLC as well as RRC client), (2) Relay RemoteRNC Protocol (RRP), and (3) Relay Host-RNC Coordination Function (HCF).

The Super-Light Relay's Host-RNC Coordination Function appears in bothfaces. It coordinates between the Host RNC's RRC impacting the Backhaulface and the relay's RRC server in the Access face. Generally theCoordination Function also accomplishes the mapping and/or transferwithin the relay between the faces of the relay. It makes use of theRemote RNC Protocol to coordinate with the host RNC.

Although Super-Light Router Relay 1108 may act (and appear) as a mobiledevice (or mobile devices) or a NodeB or an RNC from the perspective ofother network elements, there are actual differences. Note that in FIG.11 on the Access face the Relay has NodeB protocols as well as some ofthe RNC stack. However, on the Backhaul face, the Relay resembles amobile device stack, rather than a NodeB or RNC. Also note that there atleast two RRC components in the Relay (one or more for each face). TheRRC and RLC backhaul face connections are above the intermediary NodeB'sprotocol layers and thus transparent to that NodeB. Furthermore, mobiledevice 1110 does not need to know it is served by Relay 1108 as thereare no changes to the mobile device stack.

Super-Light Relay 1108 has the capability of a NodeB but also somecapabilities of an RNC. The Relay 1108 has responsibility for managingits own radio resources for those Access Link stacks (e.g., RadioResource Control (RRC)). There is thus a client RRC (or client RRCs) inthe Backhaul face and a server RRC for the Access face. However, sinceRelay 1108 only has the functionality of one NodeB (itself), the RNCfunctions for the Access Links are simplified (reduced). For example,there is no need for handoff within the Relay RNC's scope or forbackhaul protocols since the NodeB functionality may be collocated inthe Super-Light Relay 1108. Nor does Relay 1108 need to communicate withcore network 1102. Since RRP is transparent to the hosting NodeB,Tub-related problems (such as proprietary Tub implementations) are mooteven if traffic for Relay-served mobile devices is aggregated on thebackhaul.

Because Super-light Relay 1108 is responsible for Radio Resource Control(RRC) for the mobile devices it serves and handles measurement controland reporting for, it therefore has end-to-end RRC connections withthose mobile devices. This is distinct from measurement and reportingfor NodeBs, such as load and Rise-over-Thermal (RoT) information thatcan be reported by the Relay's NodeB functionality to the collocatedRelay “RNC” functionality and even over to the host RNC through the newRemote RNC Protocol (RRP).

According to some aspects, the Remote RNC Protocol (RRP) accomplishesseveral functions. First, RRP transfers user data and/or higher-layeruser control signaling between Relay 1108 and host RNC 1104. Second, RRPallows coordination between the Relay RNC functionality and the Host RNC(e.g., for the HCF).

In accordance with some aspects, the user data and higher-layer usercontrol signaling transfer by RRP may use the Iu interface employedbetween RNCs and the core network in UMTS, but carried over wirelessprotocols. However, this is unnecessary since there is a host-RNC in thepath, which can package the information received over RRP into the Iuinterface it uses to connect to the core network. Thus, there is no needto further embed (package) user data and higher-layer control signaling.However, control signaling to the Relay itself may reuse an Iur (theinter-RNC interface) or Iur-like interface, but again over wirelessprotocols for the self-backhaul part. Since the host-RNC and Relay bothhave RNC functions, this is a solution and can be improved as the Relay“RNC” is itself served by the host RNC and thus partially controlled byit.

In accordance with some aspects, Super-Light Router Relay 1108 alsoallows for the flexibility of either aggregation or non-aggregation onthe backhaul. This is discussed further below under the context ofcoordination since aggregating utilizes additional information for Relay1108 to map flows.

According to some aspects, RRP allows coordination between the hostRNC's management of the intermediary NodeB 1106 under its control (whichserves the wireless backhaul for the Relay) and Super-Light Relay 1108which manages the NodeB functions it has in order to serve mobiledevices which are on Relay 1108.

The coordination function has several components. First, Relay 1108 maps(multiplex and de-multiplex) traffic flows (such as at RLC for PDCP) toconnect flows over the backhaul to flows over the access links to mobiledevices. Second, it handles coordination of handoff to and from relay1108 in a potentially broader capacity than between actual RNCs. Third,it is responsible for measurement and reporting to host RNC 1104. Theseservices are supported by RRP messaging.

In accordance with some aspects, mapping (aggregation andnon-aggregation) is provided. To accomplish mapping between backhaulflows and access flows, relay 1108 should also coordinate prioritizationand QoS for the access link with that which the host-RNC does for thebackhaul. An advantage with this scheme is that relay 1108 has theflexibility to manage its own RLC and MAC-level flows to mobile devicesindependently of the backhaul. Relay 1108 merely needs to know whatupper-layer connections map to which mobile devices (or mobile deviceflows) so that it can transfer data between the backhaul and accessstacks. Relay 1108 may also use prioritization signaling from host-RNC1104 to prioritize and/or schedule its mobile devices. Host-RNC 1104, onthe other hand, should control the priority and/or scheduling given toflows destined to relay 1108 by intermediary (host) NodeB 1106.

When there is a one-to-one relation between relay-served mobile devicesand instances of mobile devices that the relay acts like on the backhaul(and between the individual flows to those mobile devices), thesituation is referred to herein as “non-aggregation”. In non-aggregationmode, relay acts as one mobile device per mobile device it serves, oreven one additional mobile device for control signaling destined foritself, rather than a mobile device. However, flexibility can beprovided for the relay and host-RNC to aggregate user data and signalingover the backhaul link, either by combining equal priority flows fordifferent relay served mobile devices or by letting the relay act asfewer mobile devices than the number of mobile devices it serves (oreven only as one mobile device), which is referred to as “aggregation”.Aggregation can provide “trunking efficiency” that may potentially begained when users are simultaneously active (such as mobile devices withoverlapping bursts or which have full transmit buffers).

With non-aggregation, an option is to have the relay act as multiplemobile devices or have a separate flow for control messaging destinedfor itself (as opposed to a mobile device). This may re-use relative QoSpriority levels but may need the RNC bump down the standard prioritylevel set on the intermediary NodeB to make room for one higher priorityfor RNC-to-Relay signaling. These bumped-down priority levels could thenbe translated up one by the relay for the access link. With aggregation,the backhaul could be split into N flows, where N is the cardinality ofthe union of priority levels for flows to relay served mobile devices.The relay can then extract per-mobile device messaging from each ofthose N flows and distribute to corresponding mobile device flows overaccess links. For example, all flows from all mobile devices withpriority x are aggregated into one flow over the backhaul with priorityx. Again, Relay 1108 and host RNC 1104 exchange the proper mappinginformation and, potentially, a priority translation table.

To accomplish aggregation with Router Relay 1108, there are at leastthree alternatives, which are: (1) No changes to NodeB, (2) Changes toNodeB, and (3) No Changes to NodeB/Support from RNC. For the firstalternative, without making changes to NodeB, one way aggregation can beachieved in this architecture is to map each flow of each user to aseparate MAC-d flow. The RRP can be used to set up control informationat the Router Relay, mapping a MAC-d flow to a user's flow. However,since the number of MAC-d flows per mobile device may be limited (e.g.,to about eight), this may permit only a limited amount of aggregation(e.g., sets of two or three aggregated mobile devices).

For the second alternative, by making changes to Node B, more flexibleaggregation compared to the case of No Changes to Node B (firstalternative) can be achieved. An alternative may be for the Node B toaggregate data from flows of multiple mobile devices in the same MACpacket, and add mobile device identifiers (example, H-RNTIs) to allowRemote NodeB Relay to de-multiplex downlink flows and multiplex uplinkflows. In an aspect, this alternative involves changes to the MAC-hsheader to identify the end-target and corresponding changes to the NodeB to create the header.

The third alternative for aggregation in the Router Relay case may befor the RNC to map flows of same QoS for different mobile devices to thesame MAC-d flow. As an example, a first mobile device has flows f11 andf12 with QoS priorities 1 and 2 respectively. Also, first mobile devicehas flows f21 and f22 with QoS priorities 1 and 2 respectively. Now, RNCmay set up one MAC-d flow carrying f11 and f21, and another mac-d flowcarrying f12 and f22. For this example, f11 and f21 each has QoSrequirements of 100 kbps guaranteed rate. Thus, RNC could set up thecombined MAC-d flow with a QoS requirement of 200 kbps. However, thisdoes not prevent one of the two flows from using the entire 200 kbps. Toprevent this, the RNC could run some token bucket filters to limit eachuser's rate to 100 kbps, however this would prevent a user from gettingmore than 100 kbps when system bandwidth is empty. Using moresophisticated algorithms at the RNC for traffic shaping/policing, theseissues could be handled statistically, for example. Moreover, the RNCmay in this case choose to only aggregate certain kinds of QoS flows inthe same MAC-d flow (which can more easily be policed/shaped). Thus,this option requires no changes to Node B, but needs support from theRNC in the form of sophisticated shaping/policing to appropriatelycontrol flows sharing the same MAC-d flow.

Since Router Relay looks at layers above MAC (such as RLC/PDCP),de-multiplexing of users can be done at a higher layer such as RLC (orPDCP). Note that this option is not possible in the case of Relaystrictly behaving as NodeB, since in this case relay does not look atlayers above MAC.

An advantage of the disclosed aspects is the facilitation of aggregationof mobile device traffic flows on the backhaul, although aggregation isnot required. In this aspect, NodeB may be unmodified because the RNC,being aware of the relay, can coordinate the intermediary NodeBprioritization and scheduling of mobile devices served by that NodeB andRelay. RNC can even use the flow control mechanisms of RLC to manage thequeues at NodeB.

In an aspect of aggregation, the mobile device traffic may be aggregatedon the backhaul link(s). In other words, instead of Relay acting as onemobile device per mobile device it serves (or one backhaul flow permobile device access link flow), the Relay to NodeB or Relay to RNClinks can be combined into one connection or flow. Here, NodeB does nothave to multiplex and de-multiplex as that is done at the RNC and Relayend-points

FIG. 13 illustrates a schematic representation 1300 of self-backhaulaggregation, according to an aspect. Included are an RNC 1302 and aNodeB 1304 that communicate with a first set of mobile devices 1306 overNodeB Access Links 1308, which can be wireless links. A second subset ofmobile devices 1310 communicates with a Remote NodeB Relay over RelayAccess Links 1314, which can be wireless links. Remote NodeB Relay 1312communicates with NodeB 1304 over a Self-Backhaul Link 1316, which canbe a wireless link.

RNC 1302 and Relay 1312 can alternatively use multiple flows or “Relaymobile device”-identities. RNC 1302 may inactivate or move a subset ofthe flows or identities into idle when there are no (active) mobiledevices 1310 served by relay 1312 corresponding to the characteristicsof pipe or to prioritize another pipe. Since RNC 1302 has control ofNodeB 1304 at a low MAC-hs/e level, RNC 1302 can closely coordinate theself-backhaul aggregated link with the Relay's treatment of the Relayaccess links. Also, since Relay 1312 has layers above the typical NodeB1304 (e.g. RLC), it can aggregate at or above the MAC protocol level andthereby achieve potentially superior efficiency (e.g., trunking) gain.

FIG. 14 illustrates a schematic representation 1400 of self-backhaulaggregation per priority flow, according to an aspect. In the casediscussed with reference to FIG. 13 above, or in the case ofnon-aggregation, relay 1312 may be acting as multiple mobile devicesfrom the intermediary NodeB's perspective. Thus, relay 1312 may bescheduled simultaneously on multiple channels. Relay 1312 may thus havemultiple “mobile device” identities (H-RNTIs and E-RNTIs). Relay 1312can scan multiple HS-SCCHs and watch for multiple H-RNTI assignments(and similarly for the uplink using E-RNTIs). Relay 1312 may also havesuperior demodulation or decoding processing capabilities compared to aregular (non-relaying) mobile device.

In accordance with some aspects, handoff between a relay and a regularNodeB (whether it is the host NodeB or not) is similar, in some aspects,to an inter-RNC handoff, but differs in various ways. Since the RNChosts the Super-Light Relay, it can use flow control over the RRP todiminish the handoff delay. This can be performed by controlling buffersat the Relay to empty the buffers, keep the buffers small, or coordinatebi-casting (itself being the second party) at an earlier time once theneed for handoff is determined or predicted. Thus, the handoff actiontime can be advanced (earlier) and interruption and delay can beminimized. Furthermore, the drift-RNC concept may be used to supportsoft-handoff between the Relay “RNC” and the host. Since the Iurinterface already has these capabilities, it can be used over thewireless backhaul.

It should also be noted that the drift-RNC concept may be used even withaggregation because the aggregated backhaul can carry the soft-decodedbits from mobile device transmissions (bypassing the upper layers at theRelay) to the combining point in the network.

Latency is another factor that may be considered for handoff. Eventhough there may be multiple hops for a mobile device connected to arelay, there may be less latency for that mobile device than if it wasserved by a NodeB directly if there is a scheduling advantage for mobiledevice given good geometry or link conditions to the relay on thebackhaul and prioritization on the relay access link. Thus, it may bebeneficial to communicate such information over the RRP and considerlatency in the handoff decisions.

In accordance with some aspects, there are at least four Measurement andReporting contexts when a mobile device is served by a Relay: (1)between mobile device and relay; (2) between regular (intermediary)NodeB and host RNC; (3) between relay acting as mobile devices(s) andhost RNC; and (4) between Super-Light Relay “RNC” and the host RNC.

Contexts (1) and (3) include such content as pilot strength measurements(Ec/To or the like) or event triggers. Context (1) corresponds to theaccess link while context (3) corresponds to the backhaul link. Contexts(2) and (4) include such content as RoT, load, and other conditions atthe NodeB and Relay “NodeB”.

Here, (4) is conducted over the RRP. Thus, the RRP (and the Relay andRNC coordination functions) should support exchange of informationconcerning (2) (and potentially (3), although that may be redundant andunnecessary since the source was the Relay to begin with) from RNC toRelay or of (4) from Relay to RNC (or both). When a mobile device isserved by the Relay, the Relay may thus have all the necessaryinformation to determine whether handoff should occur. Conversely, whena mobile device is served by regular NodeB, the RNC may have all thenecessary information to determine whether handoff should occur.

In accordance with some aspects, Host-RNC has a counterpart RRP in itsstack and a function to coordinate the local RRC management of resourcesused to serve the Relay as a mobile device (or mobile devices) with theRelay's (e.g., over the RRP). Host-RNC is responsible for managing thebackhaul (Iub) and wireless backhaul (NodeB) resources. Host-RNC routesuser data into flows over those links. Host-RNC keeps track of thismapping and informs Super-Light Router Relay of this mapping withassociated priorities and/or QoS parameters so that the Relay canextract these flows and map them into its own RRC-controlled flows.

According to some aspects, soft-handoff is supported. The Host-RNCshould coordinate handoff with Relay and may also support down-linksoft-handoff with the Relay acting as a Drift-RNC. In this mode, lowerlayer frames are brought back up the stack in the Host-RNC andtransported over the RRP to the Relay where the Access face upper-layersare bypassed and the lower layer frames are transmitted to the targetmobile device. This should be coordinated in time, so the Host-RNC sshould provide an action time (slot) for the Relay (or be synchronized)to transmit the frames and provide the frames sufficiently in advancefor the frames to arrive at the Relay. Thus, NodeB and Relay transmitthe frames at approximately the same time (within the search window) andmobile device can be in soft-handoff.

For uplink soft-handoff, the received lower-layer frames bypass therelay (or RNC) upper layers and are forwarded to the master RNC (eitherthe host RNC or the Super-light Relay RNC) where combining is done andthen the frames are processed by higher layers. Because of the delayover RRP, the buffers may have to be larger and jitter may be higher dueto variation in the backhaul additional delay.

One alternative is to restrict soft-handoff so that mobile devices canbe in soft-handoff with regular NodeBs or relays but not a mix of these.This can be used to control the jitter or delay variance forsoft-handoff frames. Alternatively, soft-handoff may be disallowed formobile devices currently on relays. However, note that it may beadvantageous to have relays handoff between NodeBs and potentially evenin soft-handoff even if mobile devices a relay serves are not.

Another advantage of this aspect is that the Router Relay has a distinctNodeB identity and even RNC functions, which can thus accommodate E-911emergency services. Furthermore, since the Relay's RNC signalingfunctions are collocated with the NodeB functionality, the Relay cancontrol the signaling information sent to mobile devices associated withit and this signaling is usable by the mobile device for such locationtechniques as trilateration. If the Relay is mobile and has GPSpositioning technology, then all the associated mobile devices canbenefit from this given the Relay can determine its own location andupdate a network based device which computes the location based onmobile device measurements of NodeB (and relay) transmitted signals(e.g. pilots) and NodeB (and relay) locations.

In accordance with some aspects, Super Light Router Relay can includememory operatively coupled (internally or externally) to Super LightRouter Relay. A processor can be coupled to memory and can be configuredto execute instructions retained in memory. Memory can retaininstructions related to serving at least one mobile device over awireless access link, connecting to a host radio network controller, andcommunicating with the host radio network controller with a remote radionetwork control protocol that is transparent to an intermediary basestation. Memory can also retain instructions related to mapping dataflows between a wireless backhaul link and the wireless access link withcoordination information communicated over the remote radio networkcontrol protocol. The instructions related to serving at least onemobile device can use a first physical layer, data link layer protocolstack and radio resource control server. In accordance with someaspects, the instructions related to connecting to the host radionetwork controller connects with a second physical layer, data linklayer protocol stack and a radio resource control client and theconnecting is over the wireless backhaul link to the intermediary basestation.

In accordance with some aspects, memory retains further instructionsrelated to aggregating a connection to a served mobile device withanother connection over a backhaul link and exchanging information withthe host radio network controller to map non-aggregated access links forconnections to an aggregated backhaul link. According to some aspects,memory retains further instructions related to restricting at least oneserved mobile device from being in soft-handoff and a mobile deviceserved by a base station from being in soft-handoff with a relay.

In accordance with some aspects, Super Light Router Relay includes atleast one processor (operatively connected to memory). Processorincludes a first module that serves at least one mobile device over awireless access link using a first physical layer, data link layerprotocol stack and radio resource control server. Processor alsoincludes a second module that connects to a host radio networkcontroller with a second physical layer, data link layer protocol stackand a radio resource control client over a wireless backhaul link to anintermediary base station. Further, processor includes a third modulethat communicates with the host radio network controller with a remoteradio network control protocol that is transparent to the intermediarybase station. Also included in processor is a fourth module that mapsdata flows between the wireless backhaul link and the wireless accesslink with coordination information communicated over the remote radionetwork control protocol.

FIG. 15 illustrates a schematic representation 1500 with IP Relay,according to an aspect. In accordance with some aspects, a relay gatewaywith relay self-backhaul IP is utilized when mobile device in on relayand pass-through protocols are utilized when mobile device is not onrelay. Further, a relay with base station protocols to communicate withmobile device as a base station and mobile device protocols tocommunicate with an intermediary base station (NobeB) as a mobile deviceis utilized. Relay has a relay self-backhaul IP to carry data to or froma mobile device to or from the relay gateway transparently across one ormore intermediary network elements.

Illustrated are core network elements 1502, an RNC 1504, a NodeB 1506,an IP Relay 1508 and a mobile device 1510. In accordance with someaspects, the problems discussed above are mitigated though the use of anIP Relay and a Strategic Relay Gateway (RGW). The IP Relay has NodeB andRNC protocols and functionality to serve End Users (e.g., mobiledevices) or subsequent Relays. IP Relay also has mobile device protocolsand functionality to connect to a NodeB or other Relay. IP Relay alsohas higher-layer protocols including at least IP. This IP layer will bereferred to as the Relay Self-Backhaul IP (or RSB-IP) and is below theEnd-User's IP layer but above any underlying backhaul layers (includingbackhaul UDP/IP or ATM layers). The Strategic Relay Gateway is acounterpart to the IP Relay. Three general aspects (and varioussub-options) for the Strategic Relay Gateway (RGW) are described below.The RGW works with one or more of these IP Relays or even one or more IPRelays in a multi-hop sequence of one, two, or more than two hops. Theseaspects will be described in detail starting with the IP Relay andfollowed by embodiments of the Strategic Relay Gateway (RGW).

IP Relay 1508 has at least two protocol “faces” (stacks): aself-backhaul face and an access face. There may be multiple instancesof such stacks for each face (for example one access face instance foreach mobile device 1510 served by IP relay 1508) but for purposes ofexplanation, these faces will be discussed generally.

The self-backhaul face consists of mobile device-like Physical Layer(PHY) and Medium Access Layer (MAC) protocols to connect to NodeB 1506and RNC 1504. However, on top of those layer 1 and 2 protocols, IP Relay1508 has at least a Relay Self-Backhaul IP (or RSB-IP) and may also haveUDP and GTP on top of that. This IP layer is similar to (or the same as)a mobile device (end user) IP protocol and, as far as the intermediaryNodeB 1506 or RNC 1504 are concerned, it is indiscernible from a mobiledevice. However, it is not the End User's (mobile device's) IP protocolbut rather carries the mobile device IP as data payload.

The access face consists of RNC and NodeB protocols and functionality(or partial aspects thereof) sufficient to serve a mobile device ormobile devices. From a mobile device perspective, IP Relay 1508 appearsas a NodeB. These protocol aspects are illustrated in FIG. 15 where thecore network has been abstracted for focus on the nodes in the accessstratum scope.

As illustrated, Relay Self-Backhaul IP (or RSB-IP) is transparent toNodeB 1506 and RNC 1504 because it is above the protocol processing ofthose network elements. Thus, IP Relay 1508 is generally transparent toRNC 1504 and NodeB 1506 as it generally appears as a mobile device.

The mobile device IP protocol (or whatever application protocol the useris employing) is above the Relay's Self-Backhaul IP protocol. TheRelay's Self-Backhaul IP (and UDP, GTP) protocols carry the mobiledevice IP data to and from mobile device 1510 across RNC 1504 and NodeB1506. However, note that two IP protocols (one embedded in the other)continue into core network 1502. This is in contrast to a situationwhere there is no Relay in the chain and only the mobile device's IPprotocol continues into core network 1502 (typically to the GPRS GatewaySupport Node (GGSN)), which is shown in FIG. 16. With reference to FIG.15, the underlying Relay Self-Backhaul IP is a transport for the mobiledevice's (IP) to get to and from core network 1502.

Since the underlying Relay Self-Backhaul IP is only for this purpose oftransport across the intermediary nodes transparently (the Relayappearing as if it is the End User), there should be a counterpartfunction to the IP Relay in the network side. The Strategic RelayGateway (RGW) solves this problem.

There are at least three aspects for the Strategic Relay Gateway (RGW).These different aspects relate to solving an IP routing problem. Therouting problem is one of different operations depending on whether amobile device is on a Relay or not on a Relay. However, in general theRelay Gateway coordinates the operation of the IP Relay as a forwarder(relayer) and as a served “mobile device” from the intermediary nodeperspective. This may include coordination not only of communication onthe downlink and uplink but also ancillary functions such as locationdetermination.

One perspective is that this routing problem is due to the lack of IP inNodeB or RNC. Without routing in these nodes, there is no router todistinguish and route packets from (1) mobile devices not on Relays andthose from (2) mobile devices on Relays. At the same time, changes tothe End User's equipment (UE), RNC, and NodeBs as well as core networkelements, should be mitigated.

FIG. 17 illustrates a schematic representation of a baselinearchitecture 1700 with no relays, according to an aspect. Illustratedare a mobile device 1702, a NodeB 1704, an RNC 1706, a SGSN 1708, and aGGSN 1710. This architecture may be sufficient if there are no mobiledevices on Relays because all application layer IP protocol 1712, 1714is between the mobile device and the GGSN IP.

FIG. 18 illustrates an architecture 1800 with all mobile devices on IPRelays, according to an aspect, and FIG. 19 illustrates a schematicrepresentation 1900 of protocol end-points with all mobile devices onrelays, according to an aspect. Similar to the above figure, illustratedare a mobile device 1702 a NodeB 1704, an RNC 1706, a SGSN 1708, and aGGSN 1710. In this case, a Strategic Relay Gateway (RGW 1802) could beinserted between RNC 1706 and SGSN 1708 as a counterpart for theinserted Relay Self-Backhaul IP layer at the IP Relay 1804. Here, theRelay Self-Backhaul IP 1806, 1808 is between the IP Relay 1804 andStrategic Relay Gateway (RGW 1802). That Relay Self-Backhaul IP carriesthe application IP between those points so that NodeB 1704 and RNC 1706do not need special modifications to handle the IP Relay (as it appearsas a mobile device). Finally, the application IP connection from mobiledevice 1702 to GGSN 1710 is maintained without need to modify SGSN 1708,GGSN 1710, and mobile device 1702 because those elements see theapplication IP (without the Relay Self-Backhaul IP wrapping).

However, it should be evident by comparing FIG. 17 and FIG. 18 that therouting (either through a RGW or not) would depend on whether a mobiledevice is on an IP Relay. Yet the RNC and SGSN do not have thiscapability. While the incoming (Downlink (DL)) traffic may be routedfrom a different point in or outside the core network, the outgoing(Uplink (UL)) traffic goes through the NodeB and RNC. Here, threealternatives are proposed for solving this problem (e.g., serving bothmobile devices on Relays and mobile devices not on Relays simultaneouslywith the same network design).

The three aspects to support both mobile devices on Relays and mobiledevices not on Relays are (1) Relay Non-Relay Gateway (e.g., a RelayGateway between RNC and GGSN that is capable of supporting non-Relaymobile devices), (2) Relay Access Gateway (e.g., a modified RNC capableof routing Relay UE traffic through a Relay Gateway between RNC and GGSNor bypassing the Relay Gateway for non-Relay UE traffic), and (3) RelayCore Gateway (e.g., a Relay Gateway connected to the GGSN through IPconnection(s)).

FIG. 20 illustrates a schematic representation of a Relay Non-RelayGateway, according to an aspect. Illustrated are two mobile devices2002, 2004 and a relay 2006. Also included are a NodeB 2008, an RNC2010, a RGW 2012, a SGSN 2014, and a GGSN 2016. The Relay Non-RelayGateway processes mobile device traffic for both mobile devices onRelays and Relays not on mobile devices, as the name implies. For uplinktraffic from mobile devices on Relays, Relay Non-Relay Gateway de-embedsEnd-User IP 2018 from the Relay Self-Backhaul IP (or multiple embeddedpackets thereof in the case of multiple relay hops) and forwards theEnd-User IP packets 2020 to the core network. For downlink traffic tomobile devices on Relays, Relay Non-Relay Gateway embeds End-User IPpackets into the Relay Self-Backhaul IP (or multiple embedded packetsthereof in the case of multiple relay hops) and forwards them to thefirst IP Relay through RNC 2010 and NodeB 2008. From the core-networkperspective, a Relay mobile device thus appears the same as a non-Relaymobile device from the RGW 2012 onward. Note how the Relay Self-BackhaulIP endpoints 2022, 2024 are terminated at the IP Relay 2006 and RGW2012.

An advantage of this architecture 2000 is that changes to other nodescan be mitigated (including mobile devices, NodeBs, RNC, SGSN, GGSN, andso forth). However, all packets pass through the gateway and thus canexperience additional processing delays going up one protocol face(decoding) and down the other (encoding). Thus, even mobile devices,which are not on relays, have their traffic pass through RGW 2012 andexperience those associated delays. This link referred to as a “Iu”interface, which may be time sensitive, and the link may not be tolerantof additional delay.

FIG. 21 illustrates protocols for the Relay Non-Relay Gatewayarchitecture 2100, according to an aspect. Note that the Iu connectionbetween RNC 2010 and SGSN 2102 is split into two links by the RGW 2012not just for mobile devices on Relay but for all mobile devices.

FIG. 22 illustrates a Relay Non-Relay Gateway Break-Out representation2200, according to an aspect. As mentioned above, an alternative for thecore network face is to route incoming and/or outgoing traffic to adifferent SGSN 2202 GGSN 2204 or even to include SGSN, GGSNfunctionality in the RGW, illustrated at 2206 for Relay mobile devicesas depicted in FIG. 21. However, this “break-out” concept does not avoidthe latency problem.

With reference now to FIG. 23, illustrated is a Relay Access Gatewayschematic representation 2300, according to an aspect. The Relay AccessGateway 2012 processes only traffic for mobile devices on Relays. Thisis achieved by modifying RNC 2010 to route Relay mobile device trafficthrough RGW 2302 and bypass it for non-Relay mobile devices. Generally,this can be performed by adding an IP layer with routing to RNC 2010.RGW 2302 can be addressed by IP Relay 2006 and routed there by RNC 2010,whereas other IP addresses bypass RGW 2302.

One alternative (shown in FIG. 23) is to terminate the RelaySelf-Backhaul IP at RNC 2010 (since an IP layer is added there anyway).Illustrated in FIG. 24 is a Relay Access Gateway protocol architecture2400, according to an aspect and FIG. 25 illustrates a Relay AccessGateway Break-Out 2500, according to an aspect. These aspects involvecontinuing the Relay Self-Backhaul IP to RGW 2502. In this case both IPfaces are at RNC 2010 (e.g., receive and transmit IP).

An advantage of the Relay Access Gateway is that non-Relay mobiledevices do not suffer as much additional delays. However, there is stilladditional delay because of the IP layer in RNC, which routes trafficfor mobile devices on Relays and for mobile devices not on Relays.However, compared to the above Relay Non-Relay Gateway design, there isnot an additional Iu element inserted with all the Iu stack protocols.Another advantage of the Relay Access Gateway is that there are nomodifications required for the core-network, mobile devices, or NodeBs.However, there are modifications to RNC 2010.

FIG. 26 illustrates a network design 2600 for a Relay Core Gateway forthe RGW, according to an aspect. This figure will be discussed withreference also to FIG. 27, which illustrates Relay Core GatewayProtocols from a protocol viewpoint 2700, according to an aspect, andFIG. 28, which illustrates a Relay Core Gateway Break-Out 2800,according to an aspect. Relay Core Gateway 2802 lies outside the accessstratum scope, in a sense, past the GGSN. Since GGSN has IP, it canroute IP packets. Thus, RGW 2802 can be connected directly or indirectlyto the GGSN through IP connection(s) (even a generic IP network like theinternet). IP Relay 2006 is treated by the UTRAN as a mobile device. IPtraffic of IP Relay 2006 transports End-User traffic embedded in it, butthat is transparent to NodeB 2008, RNC 2010, SGSN, and even GGSN. SinceIP Relay 2006 can address the IP RGW, only Relay mobile device trafficgoes to RGW 2502. Uplink End-User IP traffic is de-embedded by RGW 2502from the Relay Self-Backhaul IP and forwarded back to the GGSN as ifcoming from another RNC/SGSN. Downlink End-User IP is embedded intoRelay Self-Backhaul IP and forwarded back to the GGSN for transmissionto the IP Relay. The IP Relay de-embeds the End-User IP and forward tothe mobile device.

It should be noted that RGW 2502 may alternatively connect to two ormore different GGSNs because the GGSN handling for the outside networkconnection may be different from the GGSN handling the Relay and mobiledevice. In other words, the Relay Self-Backhaul IP connection passesthrough one GGSN 2702 and is routed out to the RGW 2502 then back into adifferent GGSN 2702 to be routed out of the UTRAN to a destinationnetwork (e.g. destination server or second party of a VoIP call).

There are several advantages to the aspect of FIG. 27. First, RNC,NodeB, SGSN, GGSN, and mobile device do not necessarily have to bemodified. Second, mobile devices that are not on Relays do not incuradditional delay since the Relay GW is not imposed in the connectionpath for those mobile devices.

In an alternative aspect, the Relay GW may appear to the GGSN as eithera SGSN or RNC for delivering or accepting End User IP data while at thesame time the Relay GW may appear to the GGSN as another (or the same)GGSN or RNC of delivering or accepting Relay Self-Backhaul IP data as ifit is a mobile device. In other words, the mobile device may bevirtually associated with the RGW (as if it was an RNC and NodeB) ratherthan the actual RNC and NodeB the mobile device is on). The RGW connectswith the IP Relay but the IP Relay can be treated as a mobile device onthe actual NodeB and RNC. The IP Relay then handles routing of packetsfrom that point outward (to the mobile device). In accordance with someaspects, the break-out alternative can mitigate the latency of loopingback into the GGSN and processing can be off-loaded from the corenetwork.

In accordance with some aspects, aggregation is utilized. Aggregationconsists of using a connection between the IP Relay and the RelayGateway for the traffic of multiple End User mobile devices (either forthe downlink, the uplink or both). For the downlink, the Relay Gatewaymultiplexes user traffic into one (or more) flow(s) to the IP Relaywhere the IP Relay de-multiplexes and sends the individual users' datato mobile devices. For the uplink, the IP Relay receives data fromindividual mobile devices, multiplexes user traffic into one (or more)flow(s) to the IP Relay where the Relay Gateway de-multiplexes. The IPRelay and Relay Gateway do not necessarily need to aggregate or toaggregate all users into one flow. They can aggregate groups of users orgroups of flows across users, such as users with similar QoSrequirements or user flows with similar QoS requirements. Furthermore,they can statistically aggregate on pre-allocated aggregate flowconnections (with pre-configured QoS settings), thus statisticallyavoiding usage of all (or almost) all resources by one user andmitigating connection some setup times (for the aggregate flow acrossNodeB, RNC, SGSN, and so forth).

In accordance with some aspects, IP Relay, can include memoryoperatively coupled (internally or externally) to IP Relay. A processorcan be coupled to memory and can be configured to execute instructionsretained in memory. Memory can retain instructions related to utilizingbase station protocols to communicate as a base station to a servedmobile device and mobile device protocols to communicate with anintermediary base station as a mobile device. Memory can also retaininstructions related to carrying data transparently across at least oneintermediary network element.

In accordance with some aspects, a relay gateway is connected to a firstsupport node. The data to or from the mobile device is communicated toor from the relay gateway though a relay self-backhaul internetprotocol. The relay self-backhaul internet protocol carries the data toor from the mobile device and to or from the relay gateway transparentlyacross the at least one intermediary network element. According to someaspects, the relay gateway is connected to a second support node,wherein the data to or from the mobile device is communicated to or froma destination through the second support node.

According to some aspects, IP Relay includes at least one processor(operatively connected to memory). Processor includes a first modulethat communicates with base station protocols to communicate as a basestation to a served mobile device and with mobile device protocols tocommunicate with an intermediary base station as a mobile device.Processor also includes a second module that carries data transparentlyacross at least one intermediary network element.

In view of exemplary systems shown and described above, methodologiesthat may be implemented in accordance with the disclosed subject matter,will be better appreciated with reference to various flow charts. While,for purposes of simplicity of explanation, methodologies are shown anddescribed as a series of blocks, it is to be understood and appreciatedthat the claimed subject matter is not limited by the number or order ofblocks, as some blocks may occur in different orders and/or atsubstantially the same time with other blocks from what is depicted anddescribed herein. Moreover, not all illustrated blocks may be requiredto implement methodologies described herein. It is to be appreciatedthat functionality associated with blocks may be implemented bysoftware, hardware, a combination thereof or any other suitable means(e.g. device, system, process, component). Additionally, it should befurther appreciated that methodologies disclosed throughout thisspecification are capable of being stored on an article of manufactureto facilitate transporting and transferring such methodologies tovarious devices. Those skilled in the art will understand and appreciatethat a methodology could alternatively be represented as a series ofinterrelated states or events, such as in a state diagram. Further, thevarious methods disclosed herein can include employing a processorexecuting computer executable instructions stored on a computer readablestorage medium to implement the methods.

FIG. 29 illustrates a method 2900 for routing data in a multihopcommunication network. Method 2900 can be performed by a relay. Relays,as disclosed herein provide several advantages. For example, relays canbe provided with no wired backhaul installation and/or low maintenancecosts. Relays can be fixed, portable, or mobile. Relays might havebetter antennas as compared to mobile devices. Further, relays can havearchitectures that are transparent to mobile devices and/or NodeBs.Higher-layer relays can be compatible with and have the potential toimprove position location (and E911) tirlateration. Additionally, a FDDrelay is compatible with and/or facilitated by multi-carrier HSPA+.

Method 2900 starts, at 2902, by communicating with a radio networkcontroller through an intermediary base station on behalf of a mobiledevice. The communicating can be a same signaling method as a signalingmethod used between the radio network controller and the intermediarybase station.

Method 2900 continues, at 2904, by operating as at least one servedmobile device. The operating can include using a first set of lowerlayer air interface protocol instances for a self-backhaul link betweenthe relay and the intermediary base station. In accordance with someaspects, self-backhaul link can be wireless. Additionally, the relay canact as one or more mobile devices on behalf of the mobile devices servedby the relay. The operating can also include using a second set of lowerlayer air interface protocol instances for a wireless access link to theat least one served mobile device.

In accordance with some aspects, method 2900 can continue, at 2906, withreceiving data for the at least one service mobile device and at least asecond served mobile device (or for multiple flows). The data can bereceived from an intermediary base station. The data can be received asa single flow. At 2908, the data received as the single flow isde-multiplexed. At 2910, the data is transmitted separately to the atleast one served mobile device and the at least the second served mobiledevice.

Additionally or alternatively, method 2900 can continue, at 2912, whendata is received from at least one served mobile device and at least asecond served mobile device (or from multiple flows). At 2914, the datais multiplexed to create an aggregated data. The aggregated data istransmitted, at 2916, to the intermediary base station. Transmitting theaggregated data can include acting as one mobile device (or as one userflow).

According to some aspects, radio network controller and intermediarybase station can utilize a first backhaul communication protocol. Radionetwork controller can include a second backhaul protocol above firstbackhaul protocol for communication with intermediary base station.Second backhaul can be embedded in the data transfer of first backhaulprotocol and can be terminated at the relay instead of at theintermediary base station.

In accordance with some aspects, relay contains NodeB protocols (clientsfor the backhaul link and server instances for the access links tomobile devices). Relay can also contain the RNC interfacingfunctionality, similar to a NodeB but having distinctions relating toflow mapping and/or relaying and coordination according to alternativesaspects.

In accordance with some aspects, method 2900 can be included in acomputer program product that includes a computer-readable medium (e.g.,memory) that comprises codes for carrying out various aspects. Computerreadable storage medium can include a first set of codes for causing acomputer to communicate on behalf of a mobile device with a radionetwork controller through an intermediary base station. Computerreadable storage medium can also include a second set of codes forcausing the computer to operate as at least one served flow using afirst set of lower layer air interface protocol instances and a secondset of lower layer air interface protocol instances.

In accordance with some aspects, the computer readable storage mediumincludes a third set of codes for causing the computer to receive dataas a single flow for the at least one served flow and at least a secondserved flow and a fourth set of codes for causing the computer tode-multiplex the data received as the single flow. Computer readablestorage medium can also include a fifth set of codes for causing thecomputer to transmit the data separately to the at least one served flowand the at least the second served flow.

According to some aspects, the computer readable storage medium includesa third set of codes for causing the computer to receive data from atleast two user flows. Also included is a fourth set of codes for causingthe computer to multiplex the data to create an aggregated data and afifth set of codes for causing the computer to convey the aggregateddata to the intermediary base station.

FIG. 30 illustrates a method 3000 for communicating in a multihopcommunication network. Method 3000 can be performed by a base station.Method 3000 starts, at 3002, by communicating with a radio networkcontroller with a first backhaul communication protocol andcommunicating with a relay with a second backhaul communicationprotocol. First backhaul communication protocol can include data (orsignaling) between the relay and the radio network controller. Method3000 continues, at 3004, with forwarding data (or generating signaling)for the relay on the second backhaul communication protocol based oninformation included in the first backhaul communication protocol (orvice versa). In accordance with some aspects, the intermediary basestation is an intermediary agent for the radio network controller.

In accordance with some aspects, method 3000 continues, at 3006, bydetermining a priority of transmission to the relay as a function ofpriorities of one or more mobile devices served by the relay or as afunction of a number of mobile devices served by the relay. For example,a relay is supporting three mobile devices and there are an additionalthree mobile devices reporting directly to NodeB (that hosts the relay).Thus, there are a total of six mobile devices. NodeB might not knowthere is a relay and might treat that relay as a mobile device (in thiscase, NodeB believes there are only four mobile devices, not six). Thus,the mobile devices served by the relay will not be served equally sincerelay will only receive a fourth of the priority, when it should havehalf of the priority (since there are three mobile devices served byrelay and three served by NodeB). To overcome this, the relay can betreated with a higher priority relative to the number of mobile devicesthat relay is serving. This priority can be set by the RNC, according tosome aspects. According to other aspects, the relay might have differentpriorities for its flow, thus, relay might obtain proportionally moreservice. In accordance with some aspects, intermediary base stationperforms the scheduling based on priority for a relay, which might bebased on the number of mobile devices served by the relay.

Additionally or alternatively, at 3008, a wireless communicationtechnology can be utilized by intermediary base station to communicatewith multihop communication network. In accordance with some aspects, adifferent communication can be utilized, wherein a first wirelesscommunication technology is utilized to communicate with the multihopcommunication network and a second wireless communication technology isutilized to communicate with the radio network controller. According tosome aspects, the wireless communication technology can be HSPA from amobile device to the relay and HSPA from the relay to NodeB andmicrowave can be utilized to transmit to the RNC. However, it should beunderstood that other wireless communication technologies can beutilized with the disclosed aspects and two or more wirelesscommunication technologies can be utilized in a single network.

FIG. 31 illustrates a method 3100 for conveying data in a wirelesscommunications network. Method 3100 can be performed by a relay. Method3100 starts, at 3102, when at least one mobile device is served over awireless access link. Serving the at least one mobile device can includeusing a first physical layer, data link layer protocol stack and radioresource control server.

Method 3100 continues, at 3104, with connecting to a host radio networkcontroller with a second physical layer, data link layer protocol stackand a radio resource control client. The connection can be over awireless backhaul link to an intermediary base station. In accordancewith some aspects, the data link layer protocol stack for the (accessand/or backhaul) link includes radio link control protocol includingflow control.

At 3106, method 3100 communicates with the host radio network controllerwith a remote radio network control protocol that is transparent to theintermediary base station. Data flows are mapped between the wirelessbackhaul link and the wireless access link, at 3108. The mapping isperformed with coordination information communicated over the remoteradio network control protocol.

In accordance with some aspects, method 3100 continues, at 3110, withaggregating a connection to a served mobile device with anotherconnection over a backhaul link. At 3112, information is exchanged withthe host radio network controller to map non-aggregated access links forconnections to an aggregated backhaul link.

In accordance with some aspects, host radio network controller canmanage radio resource control for the backhaul link. This can includeprioritization for the intermediary base station scheduling. Host radionetwork controller can communicate the prioritization to the relay.Further, the relay can manage radio resource control, includingprioritization for scheduling for the access link consistent with theprioritization used by the host radio network controller.

According to some aspects, measurements reports (and controls) of relayconditions are communicated to host radio network controller. Host radionetwork controller determines whether mobile device should be handed offfrom a base station (not necessarily the intermediary base station) tothe relay (or vice versa).

According to other aspects, measurements report (and controls) ofconditions of radio resources controlled by host radio networkcontroller are communicated from host radio network controller to relay.Relay determines whether mobile device should be handed off from a basestation (not necessarily the intermediary base station) to the relay (orvice versa).

In accordance with some aspects, method 3100 includes receiving, fromhost radio network controller, lower layer (MAC) frames in advance ofthose frames being forwarded (by host radio network controller) to abase station (not necessarily the intermediary base station. In thiscase, method 3100 includes bypassing the upper layers and transmits thelower layer (MAC) frames at substantially the same time as the basestation (or vice versa).

According to some aspects, in anticipation of handing off mobile deviceaway from the relay, radio network controller reduces the size of abuffer (or window) for the mobile device data at the relay bycommunicating to the relay and the handoff delay (or interruption) isthereby mitigated. In accordance with some aspects, the buffer controlis communicated over the remote radio network controller protocol andthe buffer is the radio link control flow controlled buffer.

Additionally or alternatively, method 3100 includes, restricting amobile device served by the relay from being in soft-handoff and amobile device served by a regular base station from being insoft-handoff with a relay. In accordance with some aspects, method 3100includes restricting a mobile device served by the relay from being insoft-handoff with another regular base station but not another relay. Inaccordance with some aspects, a host radio network controller canrestrict the soft-handoff.

In accordance with some aspects, method 3100 can be included in acomputer program product that includes a computer-readable medium (e.g.,memory) that comprises codes for carrying out various aspects. Computerreadable storage medium can include a first set of codes for causing acomputer to serve at least one mobile device over a wireless accesslink, wherein the serving comprises using a first physical layer, datalink layer protocol stack and radio resource control server. Alsoincluded can be a second set of codes for causing the computer toconnect to a host radio network controller with a second physical layer,data link layer protocol stack and a radio resource control client,wherein the connecting is over a wireless backhaul link to anintermediary base station. Further, computer readable storage medium caninclude a third set of codes for causing the computer to communicatewith the host radio network controller with a remote radio networkcontrol protocol that is transparent to the intermediary base station.Also included can be a fourth set of codes for causing the computer tomap data flows between the wireless backhaul link and the wirelessaccess link with coordination information communicated over the remoteradio network control protocol.

FIG. 32 illustrates a method 3200 for conveying relayed data in awireless communications network. Method 3200 can be performed by arelay. Method 3200 starts, at 3202, when base station protocols areutilized to communicate as a base station to a served mobile device. At3204, mobile device protocols are utilized to communicate (as a mobiledevice) with an intermediary base station. At 3206, data is carriedtransparently across at least one intermediary network element. Therelay can have a relay self-backhaul internet protocol to carry data toor from the mobile device and to or from a relay gateway transparentlyacross the at least one intermediary network element.

In accordance with some aspects, multi-hop cellular communicationnetwork includes a relay gateway with a relay self-backhaul internetprotocol when a mobile device is on a relay and pass-through protocolswhen a mobile device is not on a relay. The relay gateway can beconnected between a radio network controller and a support node. Data toor from the mobile device, connected to the relay, can be communicatedto or from the relay gateway through the relay self-backhaul internetprotocol. Data to or from a mobile device, not connected to the relay,can be communicated to or from the relay gateway without the relayself-backhaul protocol.

In accordance with some aspects, provided is a relay gateway withprotocols for coordinating a mobile device communication by a relaythough an intermediate base station, wherein the relay gateway processesonly data for mobile terminals that are served by relays. The relaygateway can be connected to a first support node and data to or frommobile devices connected to the relay can be communicated to or from therelay gateway by the relay self-backhaul internet protocol. The relaygateway can be connected to a second support node and to or from mobiledevices connected to the relay can be communicated to or from thedestination by the second support node. In accordance with some aspects,the first support node is the same node as the second support node.

In accordance with some aspects, the relay gateway is connected to afirst support node and data to or from mobile devices connected to therelay is communicated to or from the relay gateway by a radio networkcontroller. The radio network controller routes data to the relaygateway if the mobile device is served by the relay and the relaygateway is connected to a second support node and to or from mobiledevices connected to the relay is communicated to or from thedestination by the second support node. In accordance with some aspects,the first support node is the same node as the second support node.

In accordance with some aspects, method 3200 can be included in acomputer program product that includes a computer-readable medium (e.g.,memory) that comprises codes for carrying out various aspects. Computerreadable storage medium can include a first set of codes for causing acomputer to communicate, as a base station, with base station protocolsand to communicate as a mobile device, with mobile device protocols.Computer readable storage medium can also include a second set of codesfor causing the computer to relay data transparently across at least oneintermediary network element.

With reference to FIG. 33, illustrated is an example system 3300 thatfacilitates routing data in a multihop communication network, accordingto an aspect. System 3300 may reside at least partially within a relayand is represented as including functional blocks, which may befunctional blocks that represent functions implemented by a processor,software, or combination thereof (e.g., firmware).

System 3300 includes a logical grouping 3302 of electrical componentsthat can act separately or in conjunction. Logical grouping 3302includes an electrical component 3304 for communicating with a radionetwork controller though an intermediary base station on behalf of amobile device. Electrical component 3304 can communicate using a samesignaling method as the signaling method used between the radio networkcontroller and the intermediary base station.

Logical grouping 3302 also includes an electrical component 3306 foroperating as at least one served mobile device. Electrical component3306 can use a first set of lower layer air interface protocol instancesfor a self-backhaul link between a relay and intermediary base stationand a second set of lower layer air interface protocol instances for awireless access link to the at least one served mobile device.

In accordance with some aspects, logical grouping 3302 includes anelectrical component 3308 or receiving, from the intermediary basestation, data for the at least one served mobile device and at least asecond served mobile device. The data is received as a single flow. Alsoincluded is an electrical component 3310 for de-multiplexing the datareceived as the single flow and an electrical component 3312 fortransmitting the data separately to the at least one served mobiledevice and the at least the second served mobile device.

According to some aspects, logical grouping 3302 includes an electricalcomponent 3314 for receiving data from the at least one served mobiledevice and the at least a second served mobile device. Also included isan electrical component 3316 for multiplexing the data to create anaggregated data and an electrical component 3318 for transmitting theaggregated data to the intermediary base station.

Additionally, system 3300 can include a memory 3320 that retainsinstructions for executing functions associated with electricalcomponents 3304, 3306, 3308, 3310, 3312, 3314, 3316, and 3318 or othercomponents. While shown as being external to memory 3320, it is to beunderstood that one or more of electrical components 3304, 3306, 3308,3310, 3312, 3314, 3316, and 3318 can exist within memory 3320.

FIG. 34 illustrates an example system 3400 that facilitates conveyingdata in a wireless communications network, according to an aspect.System 3400 may reside at least partially within a relay and isrepresented as including functional blocks in a logical grouping 3402,which may be functional blocks that represent functions implemented by aprocessor, software, or combination thereof (e.g., firmware). Theelectrical components can act separately or in conjunction.

Logical grouping 3402 includes an electrical component 3404 for servingat least one mobile device over a wireless access link though use of afirst physical layer, data link layer protocol stack and radio resourcecontrol server. Also included is an electrical component 3406 forconnecting to a host radio network controller with a second physicallayer, data link layer protocol stack and a radio resource controlclient over a wireless backhaul link to an intermediary base station.

Further, logical grouping 3404 includes an electrical component 3408 forcommunicating with the host radio network controller with a remote radionetwork control protocol that is transparent to the intermediary basestation. Also included is an electrical component 3410 for mapping dataflows between the wireless backhaul link and the wireless access linkwith coordination information communicated over the remote radio networkcontrol protocol.

In accordance with some aspects, logical grouping 3402 includes anelectrical component 3412 for aggregating a connection to a servedmobile device with another connection over a backhaul link and anelectrical component 3414 for exchanging information with the host radionetwork controller to map non-aggregated access links for connections toan aggregated backhaul link. Additionally or alternatively, logicalgrouping 3402 includes an electrical component 3416 for restricting atleast one served mobile device from being in soft-handoff and a mobiledevice served by a base station from being in soft-handoff with a relay.

Additionally, system 3400 can include a memory 3418 that retainsinstructions for executing functions associated with electricalcomponents 3404, 3406, 3408, 3410, 3412, 3414, 3416, and 3418 or othercomponents. While shown as being external to memory 3418, it is to beunderstood that one or more of electrical components 3404, 3406, 3408,3410, 3412, 3414, and 3416, and 3418 can exist within memory 3418.

FIG. 35 illustrates an example system 3500 that facilitates conveyingrelayed data in a wireless communications network, according to anaspect. System 3500 may reside at least partially within a relay and isrepresented as including functional blocks in a logical grouping 3502,which may be functional blocks that represent functions implemented by aprocessor, software, or combination thereof (e.g., firmware). Theelectrical components can act separately or in conjunction.

Logical grouping 3502 includes an electrical component 3504 forcommunicating with different protocols. Base station protocols are usedto communicate as a base station to a served mobile device and mobiledevice protocols are used to communicate with an intermediary basestation as a mobile device. Logical grouping 3502 also includes anelectrical component 3506 for carrying data transparently across atleast one intermediary network element. In accordance with some aspects,system 3500 comprises a relay self-backhaul internet protocol thatcarries data to or from the mobile device and to or from a relay gatewaytransparently across the at least one intermediary network element.

System 3500 can include a memory 3508 that retains instructions forexecuting functions associated with electrical components 3404 and 3406.While shown as being external to memory 3508, it is to be understoodthat one or more of electrical components 3404 and 3406 can exist withinmemory 3508.

FIG. 36 illustrates an example system 3600 that facilitates conveyingrelayed data in a wireless communications network, according to anaspect. System 3600 may reside at least partially within a base stationand is represented as including functional blocks in a logical grouping3602, which may be functional blocks that represent functionsimplemented by a processor, software, or combination thereof (e.g.,firmware). The electrical components can act separately or inconjunction.

Logical grouping 3602 includes an electrical component 3604 forcommunicating with a radio network controller with a first backhaulcommunication protocol and with a relay with a second backhaulcommunication protocol. The first backhaul communication protocolincludes data between the relay and the radio network controller. Alsoincluded is an electrical component 3606 for forwarding the data for therelay on the second backhaul communication protocol based on informationincluded in the first backhaul communication protocol.

In accordance with some aspects, logical grouping 3602 includes anelectrical component 3608 for determining a priority of transmission tothe relay as a function of priorities of one or more mobile devicesserved by the relay or as a function of a number of mobile devicesserved by the relay. Additionally or alternatively, logical grouping3602 includes an electrical component 3610 for utilizing a firstwireless communication technology to communicate with the multihopcommunication network and a second wireless communication technology tocommunicate with the radio network controller.

System 3600 can include a memory 3612 that retains instructions forexecuting functions associated with electrical components 3604, 3606,3608, and 3610. While shown as being external to memory 3612, it is tobe understood that one or more of electrical components 3604, 3606,3608, and 3610 can exist within memory 3612.

FIG. 37 is an illustration of a system 3700 that facilitates routingdata in accordance with various aspects presented herein. System 3700comprises a base station or access point 3702. However, in accordancewith some aspects, system 3700 can be included in a relay, as discussedherein. As illustrated, base station 3702 receives signal(s) from one ormore communication devices 3704 (e.g., user device) by a receive antenna3706, and transmits to the one or more communication devices 3704through a transmit antenna 3708.

Base station 3702 comprises a receiver 3710 that receives informationfrom receive antenna 3706 and is operatively associated with ademodulator 3712 that demodulates received information. Demodulatedsymbols are analyzed by a processor 3714 that is coupled to a memory3716 that stores information related to inter-radio access technologyinterworking. A modulator 3718 can multiplex the signal for transmissionby a transmitter 3720 through transmit antenna 3708 to communicationdevices 3704.

In accordance with some aspects, system 3700 can be a computer programproduct that includes a computer-readable medium (e.g., memory 3716)that comprises codes for carrying out various aspects. Memory 3710 canstore information related to coordinating communications and any othersuitable information. Memory 3710 can additionally store protocolsassociated with relaying data.

Memory 3710 can retain instructions related to communicating with aradio network controller with a first backhaul communication protocoland with a relay with a second backhaul communication protocol, whereinthe first backhaul communication protocol includes data between therelay and the radio network controller. Memory 3710 can also retaininstructions related to forwarding the data for the relay on the secondbackhaul communication protocol based on information included in thefirst backhaul communication protocol.

In accordance with some aspects, memory 3710 retains furtherinstructions related to determining a priority of transmission to therelay as a function of priorities of one or more mobile devices servedby the relay or as a function of a number of mobile devices served bythe relay. According to some aspects, memory 3170 retains furtherinstructions related to utilizing a first wireless communicationtechnology to communicate with the multihop communication network and asecond wireless communication technology to communicate with the radionetwork controller.

It will be appreciated that data store (e.g., memories) componentsdescribed herein can be either volatile memory or nonvolatile memory, orcan include both volatile and nonvolatile memory. By way ofillustration, and not limitation, nonvolatile memory can include readonly memory (ROM), programmable ROM (PROM), electrically programmableROM (EPROM), electrically erasable ROM (EEPROM), or flash memory.Volatile memory can include random access memory (RAM), which acts asexternal cache memory. By way of illustration and not limitation, RAM isavailable in many forms such as synchronous RAM (SRAM), dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM(DRRAM). Memory of the various aspects is intended to comprise, withoutbeing limited to, these and any other suitable types of memory. Userdevice can further comprise a symbol modulator 3712, wherein transmitter3708 transmits the modulated signal.

FIG. 38 illustrates an example wireless communication system 3800. Thewireless communication system 3800 depicts one base station 3802 and onemobile device 3804 for sake of brevity. However, it is to be appreciatedthat system 3800 can include more than one base station and/or more thanone mobile device, wherein additional base stations and/or mobiledevices can be substantially similar or different from example basestation 3802 and mobile device 3804 described below. In addition, it isto be appreciated that base station 3802 and/or mobile device 3804 canemploy the systems and/or methods described herein to facilitatewireless communication there between.

At base station 3802, traffic data for a number of data streams isprovided from a data source 3806 to a transmit (TX) data processor 3808.According to an example, each data stream can be transmitted over arespective antenna. TX data processor 3808 formats, codes, andinterleaves the traffic data stream based on a particular coding schemeselected for that data stream to provide coded data.

The coded data for each data stream can be multiplexed with pilot datausing orthogonal frequency division multiplexing (OFDM) techniques.Additionally or alternatively, the pilot symbols can be frequencydivision multiplexed (FDM), time division multiplexed (TDM), or codedivision multiplexed (CDM). The pilot data is typically a known datapattern that is processed in a known manner and can be used at mobiledevice 3804 to estimate channel response. The multiplexed pilot andcoded data for each data stream can be modulated (e.g., symbol mapped)based on a particular modulation scheme (e.g., binary phase-shift keying(BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying(M-PSK), M-quadrature amplitude modulation (M-QAM), etc.) selected forthat data stream to provide modulation symbols. The data rate, coding,and modulation for each data stream can be determined by instructionsperformed or provided by processor 3810.

The modulation symbols for the data streams can be provided to a TX MIMOprocessor 3812, which can further process the modulation symbols (e.g.,for OFDM). TX MIMO processor 3812 then provides NT modulation symbolstreams to NT transmitters (TMTR) 3814 a through 3814 t. In variousembodiments, TX MIMO processor 3812 applies beamforming weights to thesymbols of the data streams and to the antenna from which the symbol isbeing transmitted.

Each transmitter 3814 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.,amplifies, filters, and upconverts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel.Further, NT modulated signals from transmitters 3814 a through 3814 tare transmitted from NT antennas 3816 a through 3816 t, respectively.

At mobile device 3804, the transmitted modulated signals are received byNR antennas 3818 a through 3818 r and the received signal from eachantenna 3818 is provided to a respective receiver (RCVR) 3820 a through3820 r. Each receiver 3820 conditions (e.g., filters, amplifies, anddownconverts) a respective signal, digitizes the conditioned signal toprovide samples, and further processes the samples to provide acorresponding “received” symbol stream.

An RX data processor 3822 can receive and process the NR received symbolstreams from NR receivers 3820 based on a particular receiver processingtechnique to provide NT “detected” symbol streams. RX data processor3822 can demodulate, deinterleave, and decode each detected symbolstream to recover the traffic data for the data stream. The processingby RX data processor 3822 is complementary to that performed by TX MIMOprocessor 3812 and TX data processor 3808 at base station 3802.

A processor 3824 can periodically determine which precoding matrix toutilize as discussed above. Further, processor 3824 can formulate areverse link message comprising a matrix index portion and a rank valueportion.

The reverse link message can comprise various types of informationregarding the communication link and/or the received data stream. Thereverse link message can be processed by a TX data processor 3826, whichalso receives traffic data for a number of data streams from a datasource 3828, modulated by a modulator 3830, conditioned by transmitters3832 a through 3832 r, and transmitted back to base station 3802.

At base station 3802, the modulated signals from mobile device 3804 arereceived by antennas 3816, conditioned by receivers 3834 a though 3834t, demodulated by a demodulator 3836, and processed by a RX dataprocessor 3838 to extract the reverse link message transmitted by mobiledevice 3804. Further, processor 3810 can process the extracted messageto determine which precoding matrix to use for determining thebeamforming weights.

Processors 3810 and 3824 can direct (e.g., control, coordinate, manage,etc.) operation at base station 3802 and mobile device 3804,respectively. Respective processors 3810 and 3824 can be associated withmemory 3840 and 3842 that store program codes and data. Processors 3810and 3824 can also perform computations to derive frequency and impulseresponse estimates for the uplink and downlink, respectively. Softwarecodes may be stored in memory unit and executed by processors 3810 and3824.

It is to be understood that aspects described herein may be implementedby hardware, software, firmware or any combination thereof. Whenimplemented in software, functions may be stored on or transmitted overas one or more instructions or code on a computer-readable medium.Computer-readable media includes both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage media may be anyavailable media that can be accessed by a general purpose or specialpurpose computer. By way of example, and not limitation, suchcomputer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to carry or store desiredprogram code means in the form of instructions or data structures andthat can be accessed by a general-purpose or special-purpose computer,or a general-purpose or special-purpose processor. Also, any connectionis properly termed a computer-readable medium. For example, if softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then coaxial cable, fiber optic cable, twisted pair, DSL, or wirelesstechnologies such as infrared, radio, and microwave are included in thedefinition of medium. Disk and disc, as used herein, includes compactdisc (CD), laser disc, optical disc, digital versatile disc (DVD),floppy disk and blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

Various illustrative logics, logical blocks, modules, and circuitsdescribed in connection with aspects disclosed herein may be implementedor performed with a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform functions described herein. Ageneral-purpose processor may be a microprocessor, but, in thealternative, processor may be any conventional processor, controller,microcontroller, or state machine. A processor may also be implementedas a combination of computing devices, for example, a combination of aDSP and a microprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration. Additionally, at least one processor may comprise one ormore modules operable to perform one or more of the steps and/or actionsdescribed herein.

For a software implementation, techniques described herein may beimplemented with modules (e.g., procedures, functions, and so on) thatperform functions described herein. Software codes may be stored inmemory units and executed by processors. Memory unit may be implementedwithin processor or external to processor, in which case memory unit canbe communicatively coupled to processor through various means as isknown in the art. Further, at least one processor may include one ormore modules operable to perform functions described herein.

Techniques described herein may be used for various wirelesscommunication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and othersystems. The terms “system” and “network” are often usedinterchangeably. A CDMA system may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), CDMA2000, etc. UTRA includesWideband-CDMA (W-CDMA) and other variants of CDMA. Further, CDMA2000covers IS-2000, IS-95 and IS-856 standards. A TDMA system may implementa radio technology such as Global System for Mobile Communications(GSM). An OFDMA system may implement a radio technology such as EvolvedUTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, Flash-OFDM®, etc. UTRA and E-UTRA are partof Universal Mobile Telecommunication System (UMTS). 3GPP Long TermEvolution (LTE) is a release of UMTS that uses E-UTRA, which employsOFDMA on downlink and SC-FDMA on uplink. UTRA, E-UTRA, UMTS, LTE and GSMare described in documents from an organization named “3rd GenerationPartnership Project” (3GPP). Additionally, CDMA2000 and UMB aredescribed in documents from an organization named “3rd GenerationPartnership Project 2” (3GPP2). Further, such wireless communicationsystems may additionally include peer-to-peer (e.g., mobile-to-mobile)ad hoc network systems often using unpaired unlicensed spectrums, 802.xxwireless LAN, BLUETOOTH and any other short- or long-range, wirelesscommunication techniques.

Single carrier frequency division multiple access (SC-FDMA), whichutilizes single carrier modulation and frequency domain equalization isa technique that can be utilized with the disclosed aspects. SC-FDMA hassimilar performance and essentially a similar overall complexity asthose of OFDMA system. SC-FDMA signal has lower peak-to-average powerratio (PAPR) because of its inherent single carrier structure. SC-FDMAcan be utilized in uplink communications where lower PAPR can benefit amobile terminal in terms of transmit power efficiency.

Moreover, various aspects or features described herein may beimplemented as a method, apparatus, or article of manufacture usingstandard programming and/or engineering techniques. The term “article ofmanufacture” as used herein is intended to encompass a computer programaccessible from any computer-readable device, carrier, or media. Forexample, computer-readable media can include but are not limited tomagnetic storage devices (e.g., hard disk, floppy disk, magnetic strips,etc.), optical disks (e.g., compact disk (CD), digital versatile disk(DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card,stick, key drive, etc.). Additionally, various storage media describedherein can represent one or more devices and/or other machine-readablemedia for storing information. The term “machine-readable medium” caninclude, without being limited to, wireless channels and various othermedia capable of storing, containing, and/or carrying instruction(s)and/or data. Additionally, a computer program product may include acomputer readable medium having one or more instructions or codesoperable to cause a computer to perform functions described herein.

Further, the steps and/or actions of a method or algorithm described inconnection with aspects disclosed herein may be embodied directly inhardware, in a software module executed by a processor, or a combinationthereof. A software module may reside in RAM memory, flash memory, ROMmemory, EPROM memory, EEPROM memory, registers, a hard disk, a removabledisk, a CD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium may be coupled to processor, such thatprocessor can read information from, and write information to, storagemedium. In the alternative, storage medium may be integral to processor.Further, in some aspects, processor and storage medium may reside in anASIC. Additionally, ASIC may reside in a user terminal. In thealternative, processor and storage medium may reside as discretecomponents in a user terminal Additionally, in some aspects, the stepsand/or actions of a method or algorithm may reside as one or anycombination or set of codes and/or instructions on a machine readablemedium and/or computer readable medium, which may be incorporated into acomputer program product.

While the foregoing disclosure discusses illustrative aspects and/orembodiments, it should be noted that various changes and modificationscould be made herein without departing from the scope of describedaspects and/or embodiments as defined by the appended claims.Accordingly, described aspects are intended to embrace all suchalterations, modifications and variations that fall within scope ofappended claims. Furthermore, although elements of described aspectsand/or embodiments may be described or claimed in the singular, theplural is contemplated unless limitation to the singular is explicitlystated. Additionally, all or a portion of any aspect and/or embodimentmay be utilized with all or a portion of any other aspect and/orembodiment, unless stated otherwise.

To the extent that the term “includes” is used in either the detaileddescription or the claims, such term is intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim. Furthermore, the term“or” as used in either the detailed description or the claims isintended to mean an inclusive “or” rather than an exclusive “or”. Thatis, unless specified otherwise, or clear from the context, the phrase “Xemploys A or B” is intended to mean any of the natural inclusivepermutations. That is, the phrase “X employs A or B” is satisfied by anyof the following instances: X employs A; X employs B; or X employs bothA and B. In addition, the articles “a” and “an” as used in thisapplication and the appended claims should generally be construed tomean “one or more” unless specified otherwise or clear from the contextto be directed to a singular form.

What is claimed is:
 1. A method performed by a relay for conveying datain a wireless communications network, comprising: employing a processorexecuting computer executable instructions stored on a computer readablestorage medium to implement: serving at least one mobile device over awireless access link, wherein the serving comprises using a firstphysical layer, data link layer protocol stack and radio resourcecontrol server; connecting to a host radio network controller with asecond physical layer, data link layer protocol stack and a radioresource control client, the connecting is over a wireless backhaul linkto an intermediary base station; communicating with the host radionetwork controller with a remote radio network control protocol that istransparent to the intermediary base station; and mapping data flowsbetween the wireless backhaul link and the wireless access link withcoordination information communicated over the remote radio networkcontrol protocol.
 2. The method of claim 1, further comprising:aggregating a connection to a served mobile device with anotherconnection over a backhaul link; and exchanging information with thehost radio network controller to map non-aggregated access links forconnections to an aggregated backhaul link.
 3. The method of claim 1,further comprising: restricting at least one served mobile device frombeing in soft-handoff and a mobile device served by a base station frombeing in soft-handoff with the relay.
 4. A wireless communicationsapparatus, comprising: a memory that retains instructions related toserving at least one mobile device over a wireless access link,connecting to a host radio network controller, communicating with thehost radio network controller with a remote radio network controlprotocol that is transparent to an intermediary base station, andmapping data flows between a wireless backhaul link and the wirelessaccess link with coordination information communicated over the remoteradio network control protocol; and a processor, coupled to the memory,configured to execute the instructions retained in the memory.
 5. Thewireless communications apparatus of claim 4, wherein the instructionsrelated to serving at least one mobile device uses a first physicallayer, data link layer protocol stack and radio resource control server.6. The wireless communications apparatus of claim 5, wherein theinstructions related to connecting to the host radio network controllerconnects with a second physical layer, data link layer protocol stackand a radio resource control client and the connecting is over thewireless backhaul link to the intermediary base station.
 7. The wirelesscommunications apparatus of claim 4, the memory retains furtherinstructions related to aggregating a connection to a served mobiledevice with another connection over a backhaul link and exchanginginformation with the host radio network controller to map non-aggregatedaccess links for connections to an aggregated backhaul link.
 8. Thewireless communications apparatus of claim 4, the memory retains furtherinstructions related to restricting at least one served mobile devicefrom being in soft-handoff and a mobile device served by a base stationfrom being in soft-handoff with a relay.
 9. A wireless communicationsapparatus, comprising: means for serving at least one mobile device overa wireless access link though use of a first physical layer, data linklayer protocol stack and radio resource control server; means forconnecting to a host radio network controller with a second physicallayer, data link layer protocol stack and a radio resource controlclient over a wireless backhaul link to an intermediary base station;means for communicating with the host radio network controller with aremote radio network control protocol that is transparent to theintermediary base station; and means for mapping data flows between thewireless backhaul link and the wireless access link with coordinationinformation communicated over the remote radio network control protocol.10. The wireless communications apparatus of claim 9, furthercomprising: means for aggregating a connection to a served mobile devicewith another connection over a backhaul link; and means for exchanginginformation with the host radio network controller to map non-aggregatedaccess links for connections to an aggregated backhaul link.
 11. Thewireless communications apparatus of claim 9, further comprising: meansfor restricting at least one served mobile device from being insoft-handoff and a mobile device served by a base station from being insoft-handoff with a relay.
 12. A computer program product, comprising: acomputer readable storage medium comprising: a first set of codes forcausing a computer to serve at least one mobile device over a wirelessaccess link, wherein the serving comprises using a first physical layer,data link layer protocol stack and radio resource control server; asecond set of codes for causing the computer to connect to a host radionetwork controller with a second physical layer, data link layerprotocol stack and a radio resource control client, the connecting isover a wireless backhaul link to an intermediary base station; a thirdset of codes for causing the computer to communicate with the host radionetwork controller with a remote radio network control protocol that istransparent to the intermediary base station; and a fourth set of codesfor causing the computer to map data flows between the wireless backhaullink and the wireless access link with coordination informationcommunicated over the remote radio network control protocol.
 13. Atleast one processor, comprising: a first module that serves at least onemobile device over a wireless access link using a first physical layer,data link layer protocol stack and radio resource control server; asecond module that connects to a host radio network controller with asecond physical layer, data link layer protocol stack and a radioresource control client over a wireless backhaul link to an intermediarybase station; a third module that communicates with the host radionetwork controller with a remote radio network control protocol that istransparent to the intermediary base station; and a fourth module thatmaps data flows between the wireless backhaul link and the wirelessaccess link with coordination information communicated over the remoteradio network control protocol.